diff options
| author | Lennart Poettering <lennart@poettering.net> | 2018-11-09 18:19:40 +0100 |
|---|---|---|
| committer | Lennart Poettering <lennart@poettering.net> | 2018-11-10 19:17:00 +0100 |
| commit | a9353a5c5b512f107955e56a9812724f40b841d3 (patch) | |
| tree | 4cd932e978677b6fccfdf0cdfe5f343b8197e026 /man/systemd.service.xml | |
| parent | 33dbab6fde5423ce61b5544ca49afa13495477a8 (diff) | |
| download | systemd-a9353a5c5b512f107955e56a9812724f40b841d3.tar.gz | |
core: log about /var/run/ prefix used in PIDFile=, patch it to be /run instead
In a way this is a follow-up for
a2d1fb882c4308bc10362d971f333c5031d60069, but adds a similar warning for
PIDFile=.
There's a much stronger case for doing this kind of notification in
tmpfiles.d (since it helps relating lines to each other for the purpose
of merging them). Doing this for PIDFile= is mostly about being
systematic and copying tmpfiles.d/ behaviour here.
While we are at it, let's also support relative filenames in PIDFile=
now, and prefix them with /run, to make them absolute.
Fixes: #10657
Diffstat (limited to 'man/systemd.service.xml')
| -rw-r--r-- | man/systemd.service.xml | 17 |
1 files changed, 9 insertions, 8 deletions
diff --git a/man/systemd.service.xml b/man/systemd.service.xml index beb4420cf0..0ce96cf3cb 100644 --- a/man/systemd.service.xml +++ b/man/systemd.service.xml @@ -272,14 +272,15 @@ <varlistentry> <term><varname>PIDFile=</varname></term> - <listitem><para>Takes an absolute path referring to the PID file of the service. Usage of this option is - recommended for services where <varname>Type=</varname> is set to <option>forking</option>. The service manager - will read the PID of the main process of the service from this file after start-up of the service. The service - manager will not write to the file configured here, although it will remove the file after the service has shut - down if it still exists. The PID file does not need to be owned by a privileged user, but if it is owned by an - unprivileged user additional safety restrictions are enforced: the file may not be a symlink to a file owned by - a different user (neither directly nor indirectly), and the PID file must refer to a process already belonging - to the service.</para></listitem> + <listitem><para>Takes a path referring to the PID file of the service. Usage of this option is recommended for + services where <varname>Type=</varname> is set to <option>forking</option>. The path specified typically points + to a file below <filename>/run/</filename>. If a relative path is specified it is hence prefixed with + <filename>/run/</filename>. The service manager will read the PID of the main process of the service from this + file after start-up of the service. The service manager will not write to the file configured here, although it + will remove the file after the service has shut down if it still exists. The PID file does not need to be owned + by a privileged user, but if it is owned by an unprivileged user additional safety restrictions are enforced: + the file may not be a symlink to a file owned by a different user (neither directly nor indirectly), and the + PID file must refer to a process already belonging to the service.</para></listitem> </varlistentry> <varlistentry> |