On Thu, 2004-01-22 at 09:40, John D. Robertson wrote: > This may sound a bit cheezy, but it would be easy to do: > > Write a script for the DHCP computer that checks the load on each of the LTSP > servers. Based on the reply (or lack of reply), this script would modify the > "/etc/dhcpd.conf" file and restart dhcpd. > > Put an entry in the crontab to run this script every minute.
Ouch! dhcpd takes a long time to restart (between 5 and 30 seconds). I wouldn't take this approach with dhcpd. A better solution is to change "-query" to "-broadcast" and have the display managers on the servers (XDM, KDM, or GDM) run a simple script that gets loadavg from each server and returns the name of the least-loaded server. You will need a third server that runs NFS only to serve home directories. While this sort of thing can be done, it gets expensive quickly and generally isn't cost effective. If you're going to buy three servers (one NFS and two LTSP), you're better off splitting the load by department or function (for example, having one server that runs OpenOffice for everyone, another that runs your browsers and email, and so on). I manage several LTSP servers for different clients, and the only downtime I've had was due to a bad network switch. -David ------------------------------------------------------- The SF.Net email is sponsored by EclipseCon 2004 Premiere Conference on Open Tools Development and Integration See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. http://www.eclipsecon.org/osdn _____________________________________________________________________ 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
