Re: ssh dropping

From: Christian Reiner (reiner@imageware.de)
Date: 06/24/02


From: Christian Reiner <reiner@imageware.de>
Date: Mon, 24 Jun 2002 12:31:03 +0200

glowe wrote:

> We have a machine that is running ssh 3.1p3 (I think that's the
> version). It runs separate from inetd. Well, for some reason when
> the daemon dies, all ssh sessions are dropped. Does anybody know why
> this happens. Even when inetd dies (I've seen it die, but not on this
> machine), current sessions stay logged in...but not with ssh. Any
> help is greatly appreciated. Thanks.
>
> g.

sshd ist the process that handles your ssh connection. When it dies it's
logical that your connection die as well.
The fact that your connections remain when inetd dies (I assume you are
talking about telnet-connections or something) is explained as follows: The
inetd (or xinetd) is NOT the daemon handling your connections it is
something like a 'super-daemon' calling the daemons actually handling your
connections. so when inetd dies after having called the connection handling
daemon that one does not die as well so your connections stay open.

Chris



Relevant Pages

  • Re: ssh dropping
    ... It runs separate from inetd. ... all ssh sessions are dropped. ... Even when inetd dies (I've seen it die, ... The fact that your connections remain when inetd dies (I assume you are ...
    (comp.security.ssh)
  • ssh dropping
    ... We have a machine that is running ssh 3.1p3 (I think that's the ... It runs separate from inetd. ... all ssh sessions are dropped. ... Even when inetd dies (I've seen it die, ...
    (comp.security.ssh)
  • ssh dropping
    ... We have a machine that is running ssh 3.1p3 (I think that's the ... It runs separate from inetd. ... all ssh sessions are dropped. ... Even when inetd dies (I've seen it die, ...
    (comp.security.ssh)
  • Re: Restarting init without rebooting
    ... The default in the new installs is not to run inetd on startup. ... A word of advice that I found on a Linux system that uses ... did NOT run it from xinetd. ... I was able to ssh into the system and found xinetd wasn't running. ...
    (comp.unix.bsd.freebsd.misc)
  • Re: Changes to hosts.allow do no affect to inetd daemons some times
    ... updating /etc/hosts.allow and changing rules for ftpd won't take affect on ... >> inetd, there is no difference. ... > You are probably seeing the effect of persistent connections: ... > Note that long running services with the TCP wrappers functionality ...
    (freebsd-questions)