diff options
| author | Joerg Behrmann <behrmann@physik.fu-berlin.de> | 2023-11-30 11:01:16 +0100 |
|---|---|---|
| committer | Luca Boccassi <luca.boccassi@gmail.com> | 2023-11-30 18:14:31 +0100 |
| commit | d4506301f945006c1619f7455b35653517b57a74 (patch) | |
| tree | dccca2922fb3d422ca73e99ab0fd4b4389d784ec /man/systemd.timer.xml | |
| parent | Make sure we close bpf outer map fd in systemd-executor (diff) | |
| download | systemd-d4506301f945006c1619f7455b35653517b57a74.tar.xz systemd-d4506301f945006c1619f7455b35653517b57a74.zip | |
man: document how to properly use a target as the Unit= of a timer
Diffstat (limited to '')
| -rw-r--r-- | man/systemd.timer.xml | 8 |
1 files changed, 5 insertions, 3 deletions
diff --git a/man/systemd.timer.xml b/man/systemd.timer.xml index 59215dc72a..e5af7c01a4 100644 --- a/man/systemd.timer.xml +++ b/man/systemd.timer.xml @@ -49,9 +49,11 @@ <para>Note that in case the unit to activate is already active at the time the timer elapses it is not restarted, but simply left running. There is no concept of spawning new service instances in this case. Due to this, services - with <varname>RemainAfterExit=</varname> set (which stay around continuously even after the service's main process - exited) are usually not suitable for activation via repetitive timers, as they will only be activated once, and - then stay around forever.</para> + with <varname>RemainAfterExit=yes</varname> set (which stay around continuously even after the service's main + process exited) are usually not suitable for activation via repetitive timers, as they will only be activated + once, and then stay around forever. Target units, which by default do not deactivate on their own, can be + activated repeatedly by timers by setting <varname>StopWhenUnneeded=yes</varname> on them. This will cause a + target unit to be stopped immediately after its activation, if it is not a dependency of another running unit.</para> </refsect1> <refsect1> |