Re: [systemd-devel] Arbitrary restrictions (e.g. for RuntimeDirectory)

2019-05-09 Thread Lennart Poettering
On Do, 09.05.19 12:22, Ulrich Windl (ulrich.wi...@rz.uni-regensburg.de) wrote: > Hi! > > I had to subscribe to this list, even though I'm no systemd > fan. Still I'll have to deal with it as the distribution we use > switched to systemd... Fantastic lead-in. This is a perfect intro if you are

Re: [systemd-devel] Arbitrary restrictions (e.g. for RuntimeDirectory)

2019-05-09 Thread Andrei Borzenkov
09.05.2019 13:22, Ulrich Windl пишет: > Hi! > > I had to subscribe to this list, even though I'm no systemd fan. Still I'll > have to deal with it as the distribution we use switched to systemd... > > I'm porting my LSB code to systemd, and I'm having some trouble. Cause of the > trouble (and

Re: [systemd-devel] Arbitrary restrictions (e.g. for RuntimeDirectory)

2019-05-09 Thread Michael Biebl
Hi Am Do., 9. Mai 2019 um 12:22 Uhr schrieb Ulrich Windl : > Despite of that I'm missing a "systemctl validate ..." command. That way I > wouldn't need to execute start, status, stop, just to find out that some > settings are rejected. There is "systemd-analyze verify". -- Why is it that

[systemd-devel] Arbitrary restrictions (e.g. for RuntimeDirectory)

2019-05-09 Thread Ulrich Windl
Hi! I had to subscribe to this list, even though I'm no systemd fan. Still I'll have to deal with it as the distribution we use switched to systemd... I'm porting my LSB code to systemd, and I'm having some trouble. Cause of the trouble (and possible reason for systemd's unpopularity) seems to