<br><br><div class="gmail_quote"><div dir="ltr">On Mon, Sep 24, 2018, 22:13 Kamil Jońca <<a href="mailto:kjonca@o2.pl">kjonca@o2.pl</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Lennart Poettering <<a href="mailto:lennart@poettering.net" target="_blank">lennart@poettering.net</a>> writes:<br>
<br>
> On Mo, 24.09.18 20:34, Kamil Jońca (<a href="mailto:kjonca@o2.pl" target="_blank">kjonca@o2.pl</a>) wrote:<br>
>> > This didn't work well enough IIRC, but if it did, then it'd provide almost postfix-like architecture.<br>
>> ><br>
>> > Or just making 'sendmail' send a SIGALRM to the main daemon would do the job perfectly well, I suspect...<br>
>> <br>
>> But I still does not know, where is the problem, why exim doest not play<br>
>> well with systemd ...<br>
><br>
> Here's an educated guess: your script terminates, so that that systemd<br>
> decides your service has ended. In such a case it kills any left-over<br>
> processes of the service, and this will include the exim process<br>
> forked off into the bg, because it is attributed to your script's<br>
> context.<br>
I made some tests (ie.add sleep at end of exec line),<br>
and this confirms your explanation.<br>
But ... why this is working as --user service? pure luck?<br></blockquote></div><div><br></div><div>Maybe the --user manager doesn't have privileges to kill a setuid-root process.</div><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
</blockquote></div>-- <br><div dir="ltr" class="gmail_signature" data-smartmail="gmail_signature"><p dir="ltr">Mantas Mikulėnas</p>
</div>