Uh. I just never noticed those. On which box do you see that? Can you reproduce this on a freshly installed box?
Svante Signell, le Wed 09 Sep 2015 08:09:11 +0200, a écrit : > 1) In more than 50% of the times of removing a socket with unink or rm > ssh/sshd hangs. When you say "removing a socket", you mean a named socket which was just created for whatever use? > 2) Starting sshd on the client normally, ssh connections are not > responding until When you mean "Starting sshd on the client", you mean running /etc/init.d/sshd restart? > task (/bin/sh(576)) increasing a bogus port 104 by 1, most probably a > bug. > task (/bin/sh(576)) deallocating a bogus port 104 by 1, most probably a > bug. I've never seen those messages for /bin/sh. > 3) When ssh connections are locked, see 2) above, logging in on the > console and > /etc/init.d/ssh stop > /etc/init.d/ssh start > usually hangs the sshd start. Breaking the start with ^C/^Z often > results in a segfault. After that sshd starts fine. Never seen that either. Samuel
