Mohamad, Mohamad Rashad wrote:
You say that "At Sun, we kill sessions only if they have been idle for several days", so my question is "How do you do that? do you use such an application like "xautolock" or you use some builtin SunRay function? and if you use a SunRay function how do you manage it? and how do you change the idle time before kill the session?
Someone in our IT department wrote an application (long ago) of which we are not particularly proud, and would certainly *not* recommend to customers. It involves a daemon that actively circumvents Xauthority security (using some knowledge which is specific to Sun's internal IT environment, and not easily generalizable) to monitor Window Manager idle time in all sessions (running as root, of course). This is a very bad idea due to the security implications.
A much better approach is to use something like xautolock within each session, although I'd still like to see somebody volunteer to rewrite xautolock to be more shared-machine-friendly. Has anyone had much experience with using xautolock on largely shared systems? How well does it scale? I haven't looked in some time, but IIRC it does some polling which is not resource-friendly, and could be improved by the addition of some IPC signaling and changing the poll interval to reflect the specified wait time (i.e. you don't need to check every second to tell whether 8 hours of idle time has elapsed yet :-).
By the way, my name is "Moham_a_d" not "Moham_e_d" ;-)
I'm very sorry, Mohamad. Regards, Bob Disclaimer: Opinions expressed in this mail are my own, and are not necessarily shared by my employer _______________________________________________ SunRay-Users mailing list [email protected] http://www.filibeto.org/mailman/listinfo/sunray-users
