Mohamed:
Note that John is using the word "kill", while you used the word
"disconnect".
If you kill a session you'll definitely free resources for sessions that
were logged in - all of the desktop applications and the X server, for
instance.
If you just disconnect a session you won't save anything, whether the
client reconnects or not.
I'm surprised however that killing a session which has been idle for 8
hours is not considered "inconveniencing ... users". At Sun, we kill
sessions only if they have been idle for several days. I'm sure the
choice of appropriate idle time depends on the usage patterns and needs
of your user community, and one size does not fit all.
Regards,
Bob
Disclaimer: Opinions expressed in this mail are my own, and are not
necessarily shared by my employer
John Shott wrote:
Mohamed:
we have a very lazy users, even to power off the clients after finish
work
Well, we seem to have lazy users in California, too. We have found,
however, that use of xautolock has greatly helped control our overall
resource use. By default, xautolock seems to allow a maximum idle
time of 60 minutes. In our case, at least, we felt that was too short
for our usage patterns .... and have it set for either 360 or 480
minutes so that we kill sessions overnight.
But we find this to be an effective way of controlling the number of
processes running without inconveniencing our users.
Good luck,
John
_______________________________________________
SunRay-Users mailing list
[email protected]
http://www.filibeto.org/mailman/listinfo/sunray-users
_______________________________________________
SunRay-Users mailing list
[email protected]
http://www.filibeto.org/mailman/listinfo/sunray-users
