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

Lennart Poettering lennart at poettering.net
Tue May 14 14:15:20 UTC 2019

On Di, 14.05.19 16:07, Ulrich Windl (Ulrich.Windl at rz.uni-regensburg.de) wrote:

> Hmm, like this:?
> > systemd-analyze verify /run/systemd/generator.late/iotwatch.target
> Failed to open /dev/tty0: Permission denied

This is mostly a cosmetical message you can safely ignore. Moreover this has long been fixed and is
not displayed on any current systemd version.

> Or more like this (in the user directory):?
> > systemd-analyze verify systemd/iotwatch.target.in
> Failed to open /dev/tty0: Permission denied
> Failed to load systemd/iotwatch.target.in: Invalid argument

That's not a valid unit file name. On systemd unit files are named in
a very strict fashion, and this is documented. A service unit file
name must be suffixed with ".service" and a target unit file name must
be suffixed with ".target". The suffix ".target.in" is not valid for a
unit file.

Yes, the error message could be better.


Lennart Poettering, Berlin

More information about the systemd-devel mailing list