[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#751636: openssh-server: ssh sessions are not cleanly termined on shutdown/restart with systemd



On Fri, Oct 10, 2014 at 06:51:20PM +0200, Tom Hutter wrote:
> If ssh is restarted, my hack does exactly the expected. The ssh user 
> sessions stay alive. Only, if the network is shut down, the sessions will be 
> terminated. Looking at this excerpt from systemd.special(7), I would say, 
> my hack does exactly the expected. What is a session depending on 
> network good, once the network has gone away?
> 
>        network.target
>            This unit is supposed to indicate when network functionality is
>            available, but it is only very weakly defined what that is supposed
>            to mean, with one exception: at shutdown, a unit that is ordered
>            after network.target will be stopped before the network -- to
>            whatever level it might be set up then -- is shut down. Also see
>            Running Services After the Network is up[1] for more information.
>            Also see network-online.target described above.

/lib/systemd/system/ssh.service in current sid has
"After=network.target" in its Unit stanza and still not cleanly kills
off ssh sessions.

There is also /lib/systemd/system/ssh@.service which seems to be
contrary to /lib/systemd/system/ssh.service which I do not understand.

> I think it's more a philosophical question, if running processes depending 
> on the network should survive a network restart

They usually did in the past, /etc/init.d/network stop;
/etc/init.d/network start returned you to the shell and did not kill
the session.

Greetings
Marc

-- 
-----------------------------------------------------------------------------
Marc Haber         | "I don't trust Computers. They | Mailadresse im Header
Leimen, Germany    |  lose things."    Winona Ryder | Fon: *49 6224 1600402
Nordisch by Nature |  How to make an American Quilt | Fax: *49 6224 1600420


Reply to: