On 02/03/07, Helmut Lichtenberg <[EMAIL PROTECTED]> wrote: > We have some basic clustering with the following setup: > All thin clients boot from one DHCP/tftp server and get their image from > there. > In their image, they run a startx script from /etc/init.d, where they get a > list of available XDMCP servers in our LAN, which are currently 3 Xeon-SMP > machines. These work as application servers for the thin clients. > The script loops through this list with xdmping and gets these parameters from > each machine: > > # xdmping ots-6 -v -t 1 > contacting 10.1.0.26... > ots-6: 13 users, load: 0.49, 0.69, 0.50 > > With some grep, awk, and sort magic the machine with the least load is chosen. > The XWindow system of the client is then started with (e.g.): [SNIP]
Sorry but can you run through this again? How is better in comparison with three peer dhcp servers running on same sub-net and answering calls from clients and running same NFS server for /home exports??? ...the one that answers quicker gets the client resulting in auto load balancing? I must admit I have not tried with three but with two servers this ran beautifully and virtually no magic script needed. I was under impression that OP wanted clustering of thin clients to increase pool of computing power but maybe I am wrong here. -- Regards, Sudev Barar ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _____________________________________________________________________ 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
