I'm new to the list and apologize if this question has been asked before. My searches have come up empty so I thought I'd ask here.
Over the Summer, I've set up an LTSP system with 10 terminals at a local elementary school where LTSP was able to save a lot of perfectly good equipment from being retired! This lab has made Linux is available to a lot of kids who wouldn't have had access to a computer this year! :) I'm running the 10 machines off a single P-III 450 with a gig of ram. I'd like to set these labs up in other schools... but the single point of failure and lack of scalability makes me nervous about the existing lab let alone a larger deployment. I'd like to add another identical P-III 450 (we have lots of these) as a load sharing and fail-over LTSP server. If one server goes down, I'd like the lab to simply slow down... not stop. I was wondering if anyone could point me at a preferred way of doing this? I have a few ideas but I'd rather not re-invent the wheel! :) My current plan is to use the Linux-HA link to ping-pong the DHCP servers on the two machines. Each time a client boots, the active server would stop it's local DHCP server and pass control to the other box. This would effectively split the load. In the event of a failure, a heartbeat script could permanently enable the surviving machine's DHCP server. The failed box could then be removed and replaced without disrupting the classroom environment. If there's an easier or better way of doing this, any suggestions would be greatly appreciated! -Tom ------------------------------------------------------- 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
