Martin Vuk wrote: > You should set password in ltsp chroot, ssh to the client and try to > get more info. > command "ps ax| grep ssh| grep socket" on the client should give you > some hints about what hangs ldm session > You should get something like > > 1872 pts/0 Ss+ 7:26 /usr/bin/ssh -X -t -M -S > /var/run/ldm_socket_vt7_192.168.31.60 [EMAIL PROTECTED] echo > LTSPROCKS ; LANG=C /bin/sh - > 1906 ? S 0:00 /usr/bin/ssh -X -t -S > /var/run/ldm_socket_vt7_192.168.31.60 -l martin 192.168.31.60 > LTSP_CLIENT=192.168.31.42 PULSE_SERVER=tcp:192.168.31.42:4713 > ESPEAKER=192.168.31.42:16001 /etc/X11/Xsession ; > /usr/sbin/ltspfsmounter all cleanup ; kill -1 $PPID > > when logged in and nothiing when logged out.
That is exactly what I'm seeing (ie: nothing on the client machine when it's logged out). Even when the client machine is shut off, I wind up with a couple of sshd processes like this: [EMAIL PROTECTED]:~$ ps ax | grep ssh 2554 ? Ss 0:00 /usr/sbin/sshd 20742 ? Ss 0:00 sshd: leon [priv] 20745 ? S 0:00 sshd: [EMAIL PROTECTED]/1 20748 pts/1 R+ 0:00 grep ssh Each unsuccessfull attempt to login will create another couple of sshd instances like those listed above (20742 and 20745) that persist even when the clients are powered off. I do have some iptables firewalling code in place on this machine, along with some customized sshd_config settings, however I've also seen this behavior on a second LTSP setup at my house, where the LTSP server is not running any iptables rules. Any other insights would be appreciated. -- Leon ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _____________________________________________________________________ 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
