On Wed, 29 Jan 2003, Anselm Martin Hoffmeister said: > Hello Cliff, > > Wednesday, January 29, 2003, 11:27:56 AM, you wrote: > > CB> Hi! > > CB> I´ve observed, if one user logs in twice or more times on different > CB> LTSP-Workstations, KDE will not work for this user without errors. > > Same with mozilla BTW. They seem not to be designed for that!? > Several people proposed to have users like "ws001"..."ws099" so that > no user is logged in twice ever.
I know that a custom script could handle the issue, but it seems that there are some existing mechanisms to deal with managing the problem. One that I've tried is via the PAM limits.conf file, which seems like an elegant way to do it, and gives control over other system resources like process scheduling priority. However, it seems to trigger only after the user has logged in, rather than preventing the login. So if a 2nd login happens under a given login id, PAM kicks in and logs the user out. In my current situation, I have xdm's Xreset calling the suicide script (which seems to work even if the ws is powered off w/o logging out - great! no hanging procs!) which unfortunately also affects the 1st (legitimate) login under that id, and all is lost :(. Of course any script that I can think of would have the same negative effect, as it would run after the 2nd login as well - so some mechanism would be required in the suicide script to distinguish between sessions as well. ---------------------------------------------------------------- John Karns [EMAIL PROTECTED] ------------------------------------------------------- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! http://www.vasoftware.com _____________________________________________________________________ Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto: https://lists.sourceforge.net/lists/listinfo/ltsp-discuss For additional LTSP help, try #ltsp channel on irc.freenode.net
