Rolf-Werner Eilert wrote: > Hi Keith, > >> When the classes logout hundreds of processes are left open. > > Didn't know LTSP 5 would produce such weird things. We're running LTSP > 4.2 and KDE on a Suse 10.3 with a very similar hardware as yours, and > this is not a problem at all. > > Maybe it's Gnome?
Nope, it's not just Gnome. I am running K12Linux 10 with KDE and I have tons of cruft left over from old sessions. One user had 5 sets of desktops running simultaneously. It appears that if the client gets rebooted the old sessions and all their processes never get killed. I just run ps -ef | grep LTSPROCKS and if you see any duplicate userIDs in there there are probably dead sessions (unless the user is logged in more than once). I think just killing the parent process (ex: ssh) should kill all the children, but I am not sure it always works. killall -u <username> may also work if you know the username of a user who has logged out but still has processes running though I have not tried that yet either. Bad: yes. I am hoping someone else knows why these processes hang around after the client disappears and can recommend a proper fix. Jeff ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _____________________________________________________________________ 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
