Systemd service life cycle

[Ralf Mardorf]

On Wed, 13 Apr 2016 07:42:00 +0200, Ralf Mardorf wrote:
>On Tue, 12 Apr 2016 19:54:29 +0200, Tom H wrote:
>>On Sun, Apr 10, 2016 at 2:23 PM, Colin Law <clanlaw at gmail.com>
>>wrote:  
>>> On 10 April 2016 at 12:08, Tom H <tomh0665 at gmail.com> wrote:    
>>>>
>>>> Does "RemainAfterExit=yes" make more than a cosmetic difference for
>>>> something like "ip link set * up"?    
>>>
>>> It makes a difference to what happens if you issue another start. If
>>> Remain is set then the start will do nothing as it is still active,
>>> if not then it will start it again.    
>>
>>Thanks! :)  
>
>[weremouse at moonstudio ~]$ man systemd.service|grep RemainAfterExit
>"[snip]
>Another use case is if a oneshot service shall not be executed
>a each time when they are pulled in as a dependency, but only
>the first time.
>[snip]"

Oops, it should read

[weremouse at moonstudio ~]$ man systemd.service|grep -B5 -A5 RemainAfterExit

or better

[weremouse at moonstudio ~]$ man systemd.service