diff options
| author | Lennart Poettering <lennart@poettering.net> | 2016-05-04 10:46:13 +0200 |
|---|---|---|
| committer | Lennart Poettering <lennart@poettering.net> | 2016-05-04 10:46:13 +0200 |
| commit | 1ed7ebcfcaa952441565c1c8c43084add1f58a89 (patch) | |
| tree | 9c2a3a4e826c8a0ebab05562d66b7070a3274dc6 /man | |
| parent | d428dd6ac9a56e7b3421fb8ef3aac9937a4a2e62 (diff) | |
| parent | dbb0578edc5ab8e11641c8b2d29904d4f5f8e1e6 (diff) | |
Merge pull request #3170 from poettering/v230-preparation-fixes
make virtualization detection quieter, rework unit start limit logic, detect unit file drop-in changes correctly, fix autofs state propagation
Diffstat (limited to 'man')
| -rw-r--r-- | man/systemd.unit.xml | 4 |
1 files changed, 3 insertions, 1 deletions
diff --git a/man/systemd.unit.xml b/man/systemd.unit.xml index abd47bd237..90a1ec6b9c 100644 --- a/man/systemd.unit.xml +++ b/man/systemd.unit.xml @@ -770,7 +770,9 @@ <command>systemctl reset-failed</command> will cause the restart rate counter for a service to be flushed, which is useful if the administrator wants to manually start a unit and the start limit interferes with that. Note that this rate-limiting is enforced after any unit condition checks are executed, and hence unit - activations with failing conditions are not counted by this rate limiting.</para></listitem> + activations with failing conditions are not counted by this rate limiting. Slice, target, device and scope + units do not enforce this setting, as they are unit types whose activation may either never fail, or may + succeed only a single time.</para></listitem> </varlistentry> <varlistentry> |