>> No, I have to confirm to add the machine to the knownhosts and to give >> the passwd for the user >> > > If you have to confirm that, then > 1) I wonder why ltsp-update-sshkeys that highvoltage proposed didn't > work for you. I followed the hints from Alkis several times:
2b) If you see an unsuccessful attempt, put those in your lts.conf: [Default] SCREEN_07=ldm SCREEN_08=shell SCREEN_DEFAULT=07 When the client boots, press Alt+Ctrl+F8 to switch to a text console. In that console, type: ssh <user>@server What confuses me about that is, any time I boot the client I get a warning that the autenticity of the host can't be established. And the question, if I want to continue, confirming that with yes, gives me the warning that the host key is permanently stored in the known hosts. After that I can log in on the F8 Text console of the client, but after rebooting "same procedure as last.." And another strange thing: I use two users for testing my wifes account and a guest accout(if visitors like to browse the net and so on, has other/less group privileges) While wifes account loggs in with the normal greetings from debian, the guest user gets an additional warning 'xhost: unable to open display ""' ------------------------------------------------------------------------------ All of the data generated in your IT infrastructure is seriously valuable. Why? It contains a definitive record of application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-d2d-c2 _____________________________________________________________________ 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
