[Bug 1304] SSH session cleanup problem

bugzilla-daemon at mindrot.org bugzilla-daemon at mindrot.org
Tue Apr 10 09:23:24 EST 2007


------- Comment #1 from dtucker at zip.com.au  2007-04-10 09:23 -------
You reboot the server, ie the one that sshd is running on, and the sshd
process survives?  Short of some kind of external checkpointing
software, I don't see how that's possible.

In its normal configuration, sshd will start as a listening process, ie
there will always be at least one sshd even if nobody has logged on via
ssh.  This is normal.

On a system that supports setproctitle (which Linux does) you will see
something like this in the process table:

# ps -eaf | grep sshd
root     25072     1  0 Apr06 ?        00:00:01 /usr/sbin/sshd
root     26965 25072  0 Apr09 ?        00:00:00 sshd: dtucker [priv]
dtucker  26967 26965  0 Apr09 ?        00:00:07 sshd: dtucker at pts/0

In this example there is one login via sshd.  Process 25072 is the
listening daemon, 26965 is the privileged process that looks after my
login and 26967 is the one that does most of the work for me.

In its normal configuration, sshd is not like, eg, telnetd which is
started from inetd.  It's possible to configure sshd to run from inetd
but it's not normally done that way (mainly because it's slower).

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

More information about the openssh-bugs mailing list