Hello Peter,

On Wed, Apr 23, 2008 at 02:45:32PM +0200, Peter Stein wrote:

> Indeed, it is only necessary to enter an IP address instead of
> "LDM_SERVER=${SERVER}" in
> /opt/ltsp/i386/usr/lib/ltsp/screen.d/ldm. 

Yes, but more easily, you can add :

     LDM_SERVER=<IP list, blank separated>

in lts.conf (on the « primary » server).


> I installed ldm on another
> machine and got the login screen. But then I receive this message:

> "This workstation isn't authorized to connect to server"
 
> There is already a workaround for this if you use a normal
> ltsp-server. But the machine ldm is supposed to connect with is not
> the ltsp server in my case. How does ssh authentications work with
> ldm? How can I fix the problem described above?  If this is solved
> and one is able to login on another machine, it should be possible
> to build a program so one can choose a machine.

It's already the case ! ldm is well designed (thanks to the LTSP
guys!) and when you specify a list of IP in LDM_SERVER as sugested
above, you'll get a chooser in the "Preferences" menu of the greeter,
from which you can select your prefered server.

For this to work, you should install the ldm_server package also on
the orther servers, exports the ssh keys, and import them on the «
primary » server, i.e. the one which contains the ltps chroot.

This documentation may be helpfull : 

http://doc.ubuntu.com/edubuntu/edubuntu/handbook/C/multiple-server-setup.html

A+

-- 

JFS.



-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference 
Don't miss this year's exciting event. There's still time to save $100. 
Use priority code J8TL2D2. 
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
_____________________________________________________________________
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