diff options
| author | Lennart Poettering <lennart@poettering.net> | 2019-07-12 09:25:22 +0200 |
|---|---|---|
| committer | Lennart Poettering <lennart@poettering.net> | 2019-07-12 14:25:28 +0200 |
| commit | bfcb9d3a7d162553d1261700b67c341aceaa9b70 (patch) | |
| tree | bff12edfafe1ca9167fb60347112c662334bf627 /man | |
| parent | b042dd687c8dc50cef6d7355d9790a2a1791ec27 (diff) | |
| download | systemd-bfcb9d3a7d162553d1261700b67c341aceaa9b70.tar.gz systemd-bfcb9d3a7d162553d1261700b67c341aceaa9b70.tar.bz2 systemd-bfcb9d3a7d162553d1261700b67c341aceaa9b70.zip | |
man: be more explicit that Type=oneshot services are not "active" after starting
Fixes: #13000
Diffstat (limited to 'man')
| -rw-r--r-- | man/systemd.service.xml | 16 |
1 files changed, 11 insertions, 5 deletions
diff --git a/man/systemd.service.xml b/man/systemd.service.xml index 145f97206c..4ff009e773 100644 --- a/man/systemd.service.xml +++ b/man/systemd.service.xml @@ -191,11 +191,17 @@ main process of the service. systemd will proceed with starting follow-up units as soon as the parent process exits.</para></listitem> - <listitem><para>Behavior of <option>oneshot</option> is similar to <option>simple</option>; however, the - service manager will consider the unit started after the main process exits. It will then start follow-up - units. <varname>RemainAfterExit=</varname> is particularly useful for this type of - service. <varname>Type=</varname><option>oneshot</option> is the implied default if neither - <varname>Type=</varname> nor <varname>ExecStart=</varname> are specified.</para></listitem> + <listitem><para>Behavior of <option>oneshot</option> is similar to <option>simple</option>; + however, the service manager will consider the unit up after the main process exits. It will then + start follow-up units. <varname>RemainAfterExit=</varname> is particularly useful for this type + of service. <varname>Type=</varname><option>oneshot</option> is the implied default if neither + <varname>Type=</varname> nor <varname>ExecStart=</varname> are specified. Note that if this + option is used without <varname>RemainAfterExit=</varname> the service will never enter + <literal>active</literal> unit state, but directly transition from <literal>activating</literal> + to <literal>deactivating</literal> or <literal>dead</literal> since no process is configured that + shall run continously. In particular this means that after a service of this type ran (and which + has <varname>RemainAfterExit=</varname> not set) it will not show up as started afterwards, but + as dead.</para></listitem> <listitem><para>Behavior of <option>dbus</option> is similar to <option>simple</option>; however, it is expected that the service acquires a name on the D-Bus bus, as configured by |