Re: I'm signed on all night, so what

Well this thread has brought up a number of good issues
for consideration. And let me add one more. The TMOUT
method that has been suggested may well be adequate.
But be aware that this only logs off idle sessions that
are at a shell prompt, not in applications.

Some people run programs or scripts that monitor the
idle time from commands like "who -u", "finger" or, "w"
and then log off idle sessions. This also can be quite
a problem, since these commands base their idea of "active"
on keyboard activity only. If you run a long cpu bound
job but have no keyboard interaction, you will show up
as idle and could then be logged off.

We ended up writing a program to monitor the cpu usage
for each user, and their child processes. That way we can
be sure the user really is idle. ADV: we sell this program,
called Logmon. You can vary the inactivity time by user,
time of day, etc. You can control how the user is logged
off. So...If you need to be sure the user processes are
really going away, you may need to consider something
like this. Send a message to logmon@xxxxxxxxxxxxxxxx for
details or visit http://www.logmon.com

Thanks!

+-----------------------------------------------------------------+
| Computronics Randy Styka |
| 4N165 Wood Dale Road Phone: 630/941-7767 |
| Addison, Illinois 60101 USA Fax: 630/941-7714 |
+-----------------------------------------------------------------+