mirror of
https://github.com/systemd/systemd-stable.git
synced 2024-12-24 21:34:08 +03:00
708961c701
As documented in systemd.path(5): When a service unit triggered by a path unit terminates (regardless whether it exited successfully or failed), monitored paths are checked immediately again, and the service accordingly restarted instantly. This commit implements this behaviour for PathExists=, PathExistsGlob=, and DirectoryNotEmpty=. These predicates are essentially "level-triggered": the service should be activated whenever the predicate is true. PathChanged= and PathModified=, on the other hand, are "edge-triggered": the service should only be activated when the predicate *becomes* true. The behaviour has been broken since at least as far back as commit |
||
---|---|---|
.. | ||
basic.target | ||
path-changed.path | ||
path-changed.service | ||
path-directorynotempty.path | ||
path-directorynotempty.service | ||
path-exists.path | ||
path-exists.service | ||
path-existsglob.path | ||
path-existsglob.service | ||
path-makedirectory.path | ||
path-makedirectory.service | ||
path-modified.path | ||
path-modified.service | ||
path-mycustomunit.service | ||
path-service.service | ||
path-unit.path | ||
paths.target | ||
sysinit.target |