Micah Cowan <[EMAIL PROTECTED]> writes: > Dan Mahoney, System Admin wrote: >> According to the manpage, screen calls /bin/lock or whatnot -- there's >> no way through .screenrc to change this (why?)...and yet the output of a >> locked screen looks significantly different from when I use lock alone. > > It uses whatever's in $LOCKPRG. Looking at the current code, it seems > the message about /usr/bin/lock and /usr/local/lck is outdated: screen > appears to always use the builtin when $LOCKPRG isn't specified (this > may be due to known bugs in common lock implementations?). Anyway, make > sure $LOCKPRG is set appropriately in the foreground screen's environment.
Are there any lurkers on the list that would care to chime in with useful examples on how they use LOCKPRG? A while back, what I wanted was the ability to blank the screen after two minutes of inactivity, and then *lock* the screen after a further sixty seconds. This would allow me to have auto-locking with a short timeout, without the annoyance of having to type my password if I look away -- because if I see the screen blank, I just tap a key to prevent it locking. Another problem I currently have with the built-in locker is that it prompts for my login password, even though I have a null login password. So it doesn't matter what I type for the first password prompt, it always accepts it. _______________________________________________ screen-users mailing list screen-users@gnu.org http://lists.gnu.org/mailman/listinfo/screen-users
