diff options
| author | Lennart Poettering <lennart@poettering.net> | 2020-10-16 18:04:59 +0200 |
|---|---|---|
| committer | Zbigniew Jędrzejewski-Szmek <zbyszek@in.waw.pl> | 2020-10-19 09:22:13 +0200 |
| commit | bb63863304795a2454a9071ebad75ee673c145d8 (patch) | |
| tree | 5745f20bd1c794481192e9c9e6c9b692515fb721 /man/systemd.service.xml | |
| parent | af4b8f8048e2d2da0b1a1a4927339cf39c62fb8a (diff) | |
| download | systemd-bb63863304795a2454a9071ebad75ee673c145d8.tar.gz | |
man: document that for Type=dbus services dropping bus name has consequences
Fixes: #17150
Diffstat (limited to 'man/systemd.service.xml')
| -rw-r--r-- | man/systemd.service.xml | 18 |
1 files changed, 12 insertions, 6 deletions
diff --git a/man/systemd.service.xml b/man/systemd.service.xml index a020214ac6..5bb13fcfe7 100644 --- a/man/systemd.service.xml +++ b/man/systemd.service.xml @@ -203,12 +203,18 @@ 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 - <varname>BusName=</varname>. systemd will proceed with starting follow-up units after the D-Bus bus name - has been acquired. Service units with this option configured implicitly gain dependencies on the - <filename>dbus.socket</filename> unit. This type is the default if <varname>BusName=</varname> is - specified.</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 + <varname>BusName=</varname>. systemd will proceed with starting follow-up units after the D-Bus + bus name has been acquired. Service units with this option configured implicitly gain + dependencies on the <filename>dbus.socket</filename> unit. This type is the default if + <varname>BusName=</varname> is specified. A service unit of this type is considered to be in the + activating state until the specified bus name is acquired. It is considered activated while the + bus name is taken. Once the bus name is released the service is considered being no longer + functional which has the effect that the service manager attempts to terminate any remaining + processes belonging to the service. Services that drop their bus name as part of their shutdown + logic thus should be prepared to receive a <constant>SIGTERM</constant> (or whichever signal is + configured in <varname>KillSignal=</varname>) as result.</para></listitem> <listitem><para>Behavior of <option>notify</option> is similar to <option>exec</option>; however, it is expected that the service sends a notification message via |