[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Some observations on ssh/sshd
From: |
Svante Signell |
Subject: |
Some observations on ssh/sshd |
Date: |
Wed, 09 Sep 2015 08:09:11 +0200 |
1) In more than 50% of the times of removing a socket with unink or rm
ssh/sshd hangs. The only way out is to break the ssh session with e.g.
~. and start again.
2) Starting sshd on the client normally, ssh connections are not
responding until
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.
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.
ps -feM|grep ssh
root 974 1 0:00.01 /usr/sbin/sshd
root 1001 974 0:00.03 /usr/sbin/sshd -R
<user> 1003 1001 0:00.01 /usr/sbin/sshd -R
- Some observations on ssh/sshd,
Svante Signell <=