Xavier Brochard wrote:
> Le Thursday 11 October 2007 20:47:16 Francis Giraldeau, vous avez écrit :
>   
>>> About the best solution I've seen is to distribute the XDMCP sessions
>>> between the servers.
>>>       
>> Yeah, that's right. Dispatching sessions on servers is realy easy to do.
>>
>> Install one server as a the "master", that will run nfsd home and client
>> root, nis (or slapd) tftpd, dhcpd and xdmcp. On other "secondary"
>> server, configure them to be client of the master server (ldap
>> authentication, mount nfs homes, etc.). Secondary servers are like
>> standard networked workstations that will be used to serve desktop
>> applications to users.
>>     
>
>   
Hmmm, we found z
> The secondary server can also have the home file system, by using ChironFS. 
> The 2 home file systems will appear as one "virtual" file system mounted on 
> the 2 servers. If the master or the slave crash, the home will still be 
> present. See http://furquim.org/chironfs/ 
>
> I didn't tried it yet, but I will !
>
> regards
>   
Hmmm, we had this running for a while on the school, remote starting 
firefox and openoffice from another server but in the end it proved more 
economical
(regarding use of resources) to have just one file/home server mounted 
nfs on both servers and do a dhcpd failover configurations. That runs 
way smoother. There are quite a bit of issues with remote apps. Think 
about security...or when you use ssh all the overhead thereoff...

-------------------------------------------------------------------------
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

Reply via email to