The problem can arise if an application gets into a CPU loop, and continually uses 100% of the CPU. It can be hard to get enough CPU time to get in as root and kill the offending process. I'm told it's not an issue on multi-processor systems. It is a pretty rare occurrence though, so I wouldn't get too worried about it.
What is maybe more of a nuisance is the habit of some browsers to crash and leave behind a pile of orphan processes - Opera is very good at doing this with plugins. If they've been running on the workstation as local apps, it's no big deal - a reboot cleans everything out. I run a little shell script via cron at some ridiculous hour of the morning which looks for user processes and kills them off - I've seen this discussed a few times on this list. John On Thu, 26 Sep 2002 08:24:46 +0800 Stephen Liu <[EMAIL PROTECTED]> wrote: > Could you please explain further how to prevent that if one > workstation locks up it will not affect the whole network. > ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _____________________________________________________________________ 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.openprojects.net
