Re: Antw: Re: Unexplainable unit restart ("Start request repeated too quickly")

[Reindl Harald <h.reindl@xxxxxxxxxxxxx>]

Am 03.06.19 um 12:30 schrieb Ulrich Windl:
>> That looks fine, though it _might_ make sense for it to have 
>> RemainAfterExit= turned on. After all, if default.target or 
>> iotwatch.target get restarted for any reason, then this unit will be 
>> started again.
> 
> That's a valuable hint: I thought systemd would remember that once started
> with success, the service is considered started until stopped manually.
> So does RemainAFterExit created a kind of dummy process that just remembers
> the state? The manual is not clear when you would need it:
> 
>        RemainAfterExit=
>            Takes a boolean value that specifies whether the service shall be
>            considered active even when all its processes exited. Defaults to
>            no.

a oneshot service without "RemainAfterExit" is not "active" for good
reasons - think about timer activated units or socket activated services
which both terminate after the last process exits and are started again
at the next event
_______________________________________________
systemd-devel mailing list
systemd-devel@xxxxxxxxxxxxxxxxxxxxx
https://lists.freedesktop.org/mailman/listinfo/systemd-devel