From: Ivan Fetch (sunmanagers@cs.du.edu)
Date: Thu May 02 2002 - 00:28:01 EDT
Hello,
We have a recurring problem with users either locking workstations
deliberately or leaving a workstation unattended long enough for it to
lock itself. Either way, the end result is a number of lab workstations
that are locked and unusable by others, which sometimes prompts folks to
unplug them or turn them off (disconnecting other folks who are ssh'ed in
remotely)...
I've been playing with various potential cron jobs that try to
determine whether a workstation has been locked for longer than X number
of minutes, and do something like kill the user's dtsession process. The
only way I can tell when a workstation is seemingly locked is bythe the
existance of a dtscreen process (screen saver) although maybe it's
possible that dtscreen could be running and the workstation could be
"unlocked." I don't want to disable the ability to lock workstations
entirely, but I do want to keep folks from being able to tie up a
workstation for longer than X minutes.
Does anyone have experience with this problem? I'd rather a solution
that is a kind of wrapper around the locking process which could monitor
how long the workstation has been locked and then log out the user after X
number of minutes. Maybe something could be crafted with CDE actions or
the locking process that dtsession seems to launch could be replaced with
something like xlockmore that does an autologout?
Thanks for any experiences and suggestions,
I'll summarize.
Ivan Fetch.
_______________________________________________
sunmanagers mailing list
sunmanagers@sunmanagers.org
http://www.sunmanagers.org/mailman/listinfo/sunmanagers
This archive was generated by hypermail 2.1.7 : Wed Apr 09 2008 - 23:24:16 EDT