Hi, >>> For simple loadbalancing, maybe I would let the LDM_SERVER as is and >>> create a new variable for matter, for example : LDM_SERVERS_LIST. I >>> understand that for simple loadbalancing, servers state won't be used >>> and only a randomize on the list will be done. That's good and scalable. >>> But at least, a server that is down should be automaticaly removed from >>> the list. >>> >> Well, I don't particularily like the idea of two variables, as then it >> becomes >> unclear for users as to what variable does what, and becomes a support issue >> later on. >>
It's okay, let's do it like this. We should keep in mind the fact that a server in the list may be down and manage it accordingly. A good way to do it would be to trap ssh connexion error and retry with another server in the list. If no servers are available, a message should be shown to the user to inform that it won't be able to start a session. I'm dedicated to that this week. Have a nice day, Francis Giraldeau ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _____________________________________________________________________ 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
