d7cf8c24d4ef6ed4c9d711ee82ba57a529baad34
Our handling of the condition was inconsistent. Normally, we'd only fire when the file was created (or removed and subsequently created again). But on restarts, we'd do a "recheck" from path_coldplug(), and if the file existed, we'd always trigger. Daemon restarts and reloads should not be observeable, in the sense that they should not trigger units which were already triggered and would not be started again under normal circumstances. Note that the mechanism for checks is racy: we get a notification from inotify, and by the time we check, the file could have been created and removed again, or removed and created again. It would be better if we inotify would give as an unambiguous signal that the file was created, but it doesn't: IN_DELETE_SELF triggers on inode removal, not directory entry, so we need to include IN_ATTRIB, which obviously triggers on other conditions. Fixes #12801.
…
…
…
…
…
…
…
…
systemd - System and Service Manager
Details
General information about systemd can be found in the systemd Wiki.
Information about build requirements is provided in the README file.
Consult our NEWS file for information about what's new in the most recent systemd versions.
Please see the Hacking guide for information on how to hack on systemd and test your modifications.
Please see our Contribution Guidelines for more information about filing GitHub Issues and posting GitHub Pull Requests.
When preparing patches for systemd, please follow our Coding Style Guidelines.
If you are looking for support, please contact our mailing list or join our IRC channel.
Stable branches with backported patches are available in the stable repo.
Languages
C
88.5%
Shell
5.7%
Python
4.6%
Meson
1.1%