]> git.ipfire.org Git - thirdparty/systemd.git/commit
man: clarify that ExecCondition= skip triggers SuccessAction=
authorRocker Zhang <zhang.rocker.liyuan@gmail.com>
Fri, 15 May 2026 11:27:57 +0000 (19:27 +0800)
committerZbigniew Jędrzejewski-Szmek <zbyszek@amutable.com>
Wed, 27 May 2026 12:05:08 +0000 (14:05 +0200)
commit90e3b4cb2653f8a96512da625eb92bc72607a136
tree0aefeb957057acb156bf8177fd48a8d9a51e7368
parentb130084a2d87f0cca266383f8963d11532b0cff7
man: clarify that ExecCondition= skip triggers SuccessAction=

Unit-level Condition…= / Assert…= directives that fail prevent activation
entirely, so SuccessAction= / FailureAction= never fire. An ExecCondition=
skip in [Service] runs as part of the activation transition itself, so
the unit goes active → inactive and SuccessAction= is honored.

This asymmetry has tripped users up; document it explicitly in both
systemd.service(5) (ExecCondition= section) and systemd.unit(5)
(SuccessAction= / FailureAction= section) with cross-references.

Fixes: https://github.com/systemd/systemd/issues/42035
Co-developed-by: Claude Opus 4.7 <noreply@anthropic.com>
man/systemd.service.xml
man/systemd.unit.xml