06.10.2018 16:42, Ralf Sieger пишет: > Yes, restart of the whole system. User sessions are run outside of ssh service in own scope and belong to user slice which is terminated separately during shutdown. Since v239 it is possible to add drop-ins to user slices and scopes which allows you to order some barrier service after them. > Regards, > > Ralf > *Gesendet:* Samstag, 06. Oktober 2018 um 05:46 Uhr > *Von:* "Andrei Borzenkov" <arvidjaar@xxxxxxxxx> > *An:* systemd-devel@xxxxxxxxxxxxxxxxxxxxx > *Betreff:* Re: require=? to prevent premature session termination > 05.10.2018 15:52, Ralf Sieger пишет: > > Hi, > > my service needs to delay the stop of ssh during shutdown. > > New ssh connections while my service is still runnign must be accpted, too. > > So far I was able to postpone the stop of ssh and allow new connections: > > [Unit] > > BindsTo=ssh.service getty.target > > After=ssh.service getty.target > > [Service] > > Type=simple > > TimeoutStopSec=600 > > ExecStart=/usr/local/bin/rbs > > [Install] > > WantedBy=multi-user.target > > The remaining problem is that upon shutdown/restart existing ssh users still get > > disconnected. > > Shutdown/restart of what? The whole system? > > > How can I that postpone, too? or, better: what is the missing depdency? > > Any ideas? > > Regards, > > > > Ralf > > > > > > > > _______________________________________________ > > systemd-devel mailing list > > systemd-devel@xxxxxxxxxxxxxxxxxxxxx > > https://lists.freedesktop.org/mailman/listinfo/systemd-devel > > > > _______________________________________________ > systemd-devel mailing list > systemd-devel@xxxxxxxxxxxxxxxxxxxxx > https://lists.freedesktop.org/mailman/listinfo/systemd-devel > _______________________________________________ systemd-devel mailing list systemd-devel@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/systemd-devel