You can query your X server directly with its canonical name instead of ip address. This same name should point to your four servers in your dns. I think the less loaded server will respond first. After some clients have logged in, this server could no more be the less loaded and thus will not be able to respond to x client as rapidly as it did before. Another server which is now the less loaded will probably be the first to respond to queries.
You should have set up your servers in a way that you don't need to sync user home directories (/home mounted through nfs on all servers is one solution). Fathi Ben nasr Randall Craig a écrit : > Probably the easiest way is to you xdm indirect broadcasts. > > ie: x -indirect foo > > This allows for the user to choose which server to log into. With > my setup (SusE) the xdm servers state what the load on the machines > are, and the user can choose respectively. > > You can also to failsafe measures such as rsync or inter-mezzo to > sync users hard-drives on the different machines in case one server > goes down. > > If you need some help on this contact me. > > -- Randall > > * Zoilo ([EMAIL PROTECTED]) [020821 03:24]: > > On Wednesday 21 August 2002 05:00, George Hart wrote: > > > Hi, > > > > > > I am in a situation where my company will need to have at least four > > > terminal servers to balance the load in the office. While ltsp works > > > really good, I am having trouble figuring how to load balance these > > > servers in a scaleable way. > > > > > > I took a look at clustering the servers (openmosix) but decided against > > > it because it appears that if one node goes down then the whole cluster > > > can fail. This is too unrealiable for me. > > > > > > Currently I am considering hacking etherboot to balance where it gets > > > the kernel from tftp. I am not sure how easy that would be, so I > > > thought I would post a question before I do something unusal. > > > > > > Is anyone aware of a good way to balance the load across terminal servers? > > > > I have not (yet) done this, but would think of the following method: > > > > => use only one machine as the DHCP server and TFTP-server > > => in /etc/dhcpd.conf create a group for each cluster > > => in the group specify "root-path "<cluster-server-name>:/opt/ltsp/i386" > > > > If you like your clusters to get the kernels from their own cluster-server, > > you can use 'next-server "<cluster-server-name>:/lts/vmlinuz-2.4.9-6'. > > > > Zoilo. > > > > > > ------------------------------------------------------- > > This sf.net email is sponsored by: OSDN - Tired of that same old > > cell phone? Get a new here for FREE! > > https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390 > > _____________________________________________________________________ > > 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 > > ------------------------------------------------------- > This sf.net email is sponsored by: OSDN - Tired of that same old > cell phone? Get a new here for FREE! > https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390 > _____________________________________________________________________ > 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 ------------------------------------------------------- This sf.net email is sponsored by: OSDN - Tired of that same old cell phone? Get a new here for FREE! https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390 _____________________________________________________________________ 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
