Lennart Poettering writes:
> On Wed, 15.10.14 11:07, Jan Synacek (jsyna...@redhat.com) wrote:
>
>> Hello,
>>
>> in the documentation for systemd.service, under Type= option, it reads:
>>
>> Behavior of oneshot is similar to simple; however, it is expected that the
>> process has to exit befo
On Wed, 15.10.14 11:07, Jan Synacek (jsyna...@redhat.com) wrote:
> Hello,
>
> in the documentation for systemd.service, under Type= option, it reads:
>
> Behavior of oneshot is similar to simple; however, it is expected that the
> process has to exit before systemd starts follow-up unit Rema
Mantas Mikulėnas writes:
> On Oct 15, 2014 12:07 PM, "Jan Synacek" wrote:
>>
>> Hello,
>>
>> in the documentation for systemd.service, under Type= option, it reads:
>>
>> Behavior of oneshot is similar to simple; however, it is expected that
> the
>> process has to exit before systemd starts
On Oct 15, 2014 12:07 PM, "Jan Synacek" wrote:
>
> Hello,
>
> in the documentation for systemd.service, under Type= option, it reads:
>
> Behavior of oneshot is similar to simple; however, it is expected that
the
> process has to exit before systemd starts follow-up unit
RemainAfterExit=
> i
Hello,
in the documentation for systemd.service, under Type= option, it reads:
Behavior of oneshot is similar to simple; however, it is expected that the
process has to exit before systemd starts follow-up unit RemainAfterExit=
is particularly useful for this type of service. This is the im
