<html><head></head><body><div style="font-family: Verdana;font-size: 12.0px;"><div>Hm, according to the docs this is not the case:</div>
<div>"if a unit is configured with <code class="varname">After=</code> on another unit, the former is stopped before the latter if both are shut down "</div>
<div>I read this as:</div>
<div>a has After=b</div>
<div>then the start ording should be:</div>
<div>1. start b</div>
<div>2. start a</div>
<div>and thus the reverse on shutdown should be</div>
<div>
<div>1. stop a</div>
<div>2. stop b</div>
<div>Which is what I want. I wannt to be stopped first.</div>
<div> </div>
<div>I have only the problem that existing ssh sessions get terminated before the stop reaches my service.</div>
<div>SSH itself keeps runnign and I can login.</div>
</div>
<div> </div>
<div class="signature">Regards,<br/>
<br/>
Ralf</div>
<div>
<div>
<div name="quote" style="margin:10px 5px 5px 10px; padding: 10px 0 10px 10px; border-left:2px solid #C3D9E5; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">
<div style="margin:0 0 10px 0;"><b>Gesendet:</b> Freitag, 05. Oktober 2018 um 15:03 Uhr<br/>
<b>Von:</b> "Reindl Harald" <h.reindl@thelounge.net><br/>
<b>An:</b> systemd-devel@lists.freedesktop.org<br/>
<b>Betreff:</b> Re: [systemd-devel] require=? to prevent premature session termination</div>
<div name="quoted-content"><br/>
<br/>
Am 05.10.18 um 14:52 schrieb Ralf Sieger:<br/>
> my service needs to delay the stop of ssh during shutdown.<br/>
> New ssh connections while my service is still runnign must be accpted, too.<br/>
> <br/>
> So far I was able to postpone the stop of ssh and allow new connections:<br/>
> [Unit]<br/>
> BindsTo=ssh.service getty.target<br/>
> After=ssh.service getty.target<br/>
> <br/>
> [Service]<br/>
> Type=simple<br/>
> TimeoutStopSec=600<br/>
> ExecStart=/usr/local/bin/rbs<br/>
> <br/>
> [Install]<br/>
> WantedBy=multi-user.target<br/>
> <br/>
> The remaining problem is that upon shutdown/restart existing ssh users<br/>
> still get disconnected.<br/>
> How can I that postpone, too? or, better: what is the missing depdency?<br/>
<br/>
well, when you say "After=ssh.service" you get started after ssh at boot<br/>
and since shutdown is the reverse order ssh is terminated before your<br/>
service<br/>
<br/>
so i would just say "Before=ssh.service" instead "After=ssh.service" ,<br/>
in that case ssh connections are only accepted after your service is<br/>
started and ssh is not killed as long your service is running<br/>
<br/>
you can have only one of both<br/>
<br/>
it's impossible to decalre a different order at boot and at shutdown<br/>
becaus eit makes no sense - you express ordering meaning "x makes only<br/>
sense after y is started" and the logical consequence is that the<br/>
sutdown acts in reverse order<br/>
<br/>
when you say "After=myqld" you wan't to get started after mysqld because<br/>
your service can't live wothout, so it amkes zero sense at shutdown kill<br/>
mysqld first and then your service, given it's a webserver depending on<br/>
a working database otherwise it would accept new client connections it<br/>
can't handle<br/>
_______________________________________________<br/>
systemd-devel mailing list<br/>
systemd-devel@lists.freedesktop.org<br/>
<a href="https://lists.freedesktop.org/mailman/listinfo/systemd-devel" target="_blank">https://lists.freedesktop.org/mailman/listinfo/systemd-devel</a></div>
</div>
</div>
</div></div></body></html>