On 27/03/18 15:06, Aaron Conole wrote:
> There are a few advantages (and some disadvantages, also).
>
> One thing that's nice is systemd will clean up the directories when the
> service ends. I realize that /run is usually tmpfs, but it's nice that
> they don't linger - even if ovs-lib "breaks in
Markos Chandras writes:
> On 27/03/18 14:34, Aaron Conole wrote:
>>
>> Systemd has fixed this with commit:
>>
>> 30c81ce2cef9 ("pid1: when creating service directories, don't chown existing
>> files")
>>
>> Which was caught thanks to some proactive testing:
>>
>> https://bugzilla.redhat.com/
On 27/03/18 14:34, Aaron Conole wrote:
>
> Systemd has fixed this with commit:
>
> 30c81ce2cef9 ("pid1: when creating service directories, don't chown existing
> files")
>
> Which was caught thanks to some proactive testing:
>
> https://bugzilla.redhat.com/show_bug.cgi?id=1508495
>
> I think
Markos Chandras writes:
> It appears that new systemd versions (tested with v237) changed the
> way RuntimeDirectory option behaves. Upstream commit 3536f49e8fa2
> ("core: add {State,Cache,Log,Configuration}Directory=") modified the
> RuntimeDirectory code to run before every ExecStart* command i
It appears that new systemd versions (tested with v237) changed the
way RuntimeDirectory option behaves. Upstream commit 3536f49e8fa2
("core: add {State,Cache,Log,Configuration}Directory=") modified the
RuntimeDirectory code to run before every ExecStart* command instead
of running it once per serv
