K12LTSP is based on RedHat, and the current K12 iso set is using RH8.0. It is a highly stable and EXTREEMLY cost effective alternative to a lab full of windows boxes.
pico /etc/sysconfig/desktop
DESKTOP="GNOME" DISPLAYMANAGER="KDE"
My client setup uses IceWM (on top of the KDE displaymanager, I think is the way it goes, so gnome is by-passed for IceWM). It is much lighter than the other options, and very stable.
"...
don't all the X processes die as soon as the
local X server dies? Perhaps you could explain this problem in more detail...."
What is happening, is that if a student just hits reset while they are logged onto a client, the box will reboot, and they are long gone. The processes like office and the web browser will still be sitting on the server taking up valueable ram. A number of administrators are using kill scripts that run at log off (to be sure that any hung processes will be killed), but the scripts only run if the user actually logs off properly.
Each class one or two users will almost certainly leave a box by resetting rather than logging off, and after several classes, this will really pile up processes and ram. By running top or ps we can find these processes, by owner, and the only way currently to automate this problem (in some manner) is to ask those 'reset-button-pushers' to please log back on, then off again, to allow the kill scripts to efficiently run and kill off everything that belonged to them.
one such script example is:
#!/bin/sh
#Suicide!
#this is GPL software, read the license at www.gnu.org
#by Carlos Urbieta Cabrera
#a change suggested by John et al
if [ $USER != root ]; then
kill -9 `ps aux | grep $USER | awk '{print $2}'`
fiI use this one, and it works well, but only if I can get the students to log off, as it is executed as part of the log off cycle (it is actually the whole cycle!).
I hope that this has explained things better.
Jim
Message: 3 From: Michael Wardle <michael.wardle@xxxxxxxxxx> Organization: Adacel Technologies To: psyche-list@xxxxxxxxxx Subject: Re: script to check before 2nd process executes Date: Wed, 12 Mar 2003 16:50:53 +1100 Reply-To: psyche-list@xxxxxxxxxx
On Wednesday, March 12, 2003 16:31, Jim Christiansen wrote:
Several (probably many others too) on the K12OSN list (this is for Linux Thin Servers/Clients in Education) have been having a problem with students clicking away on icons impatiently and starting too many processes with the result that things tend to become totally screwed up (sorry for the s word).
The next stable release of Red Hat Linux (8.1) will have a feature called startup notification, so that you get a busy cursor and/or a message so that you know the program is starting. This has also been available in KDE for a while. Is LTSP based on Red Hat?
One: that can stop a second duplicate application from starting.
I can't think of anything simple right now.
Two: another that can somehow kill processes if a client is just reset rather than logged off?
Doesn't the LTSP start a local X server then connect to a remote machine using
XDMCP? If this is the case, don't all the X processes die as soon as the
local X server dies? Perhaps you could explain this problem in more detail.
-- Michael Wardle Adacel Technologies
_________________________________________________________________
MSN 8 helps eliminate e-mail viruses. Get 2 months FREE*. http://join.msn.com/?page=features/virus
-- Psyche-list mailing list Psyche-list@xxxxxxxxxx https://listman.redhat.com/mailman/listinfo/psyche-list
