Don't use the cycle/period

[Steven Allen]

So, from the documentation, it looks like xss-lock uses the period (cycle) for determining how far in advance to notify the user that the screen will be locked. Instead it should use a fixed (configurable?) delay or just wait for the notification program to exit. The period is the interval at which the screensaver image should be changed and doesn't apply to screen locking. It dates back to a time when one needed to periodically change the image on the screen to prevent burn-in.

[Link]

This isn't a bug nor is it a problem.

It's merely clever use of a vestigial X11 feature. It reduces the amount of code needed in xss-lock and reduces the number of things xss-lock users need to configure.

What justification do you have other than "this isn't the originally intended function"?

[Steven Allen]

IIRC, I ran across some tools that tried to set the to set the screen lock delay and ended up messing with the cycle; however, I honestly can't remember what. I could have just been confused and annoyed that the cycle was being repurposed (it would be nice to explain this in the manual) but I can't remember at this point.

Given that I completely forgot that I filed this issue and have been using xss-lock for several months now, I'll just close this issue. Sorry about that.