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

Ulrich Windl Ulrich.Windl at rz.uni-regensburg.de
Mon May 13 06:28:22 UTC 2019


>>> Lennart Poettering <lennart at poettering.net> schrieb am 09.05.2019 um 17:28
in
Nachricht <20190509152826.GD5854 at gardel-login>:
> On Do, 09.05.19 15:52, Ulrich Windl (Ulrich.Windl at rz.uni‑regensburg.de)
wrote:
> 
>> (Sorry, I didn't sent to the list before)
>> >>> Ulrich Windl <Ulrich.Windl at rz.uni‑regensburg.de> schrieb am 09.05.2019
um 
> 14:25
>> in Nachricht <5CD44C9A.ED38.00A1.0 at rz.uni‑regensburg.de>:
>> >>>> Michael Biebl <mbiebl at gmail.com> schrieb am 09.05.2019 um 12:26 in
Nachricht
>> > <CAGWsdOi_9z8XBrQTyh0wGNJxP3JZKhs8gQeRXvJPo3ZriLRdTw at mail.gmail.com>:
>> > > Hi
>> > >
>> > > Am Do., 9. Mai 2019 um 12:22 Uhr schrieb Ulrich Windl
>> > > <Ulrich.Windl at rz.uni‑regensburg.de>:
>> > >
>> > >> 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".
>>
>> > That sounds interesting, but it seems I'll have to be root to use
>> > it, and
> 
> These limitations where lifted a long time ago. Please update.

It's good to hear, unfortunatey I'm unable to do that (enterprise environment
with certified software).

Regards,
Ulrich






More information about the systemd-devel mailing list