Adrian Vovk 720c618397 core: path: Re-enter waiting if target is deactivating ... Previously, path units would remain in the running state while their target unit is deactivating. This left a window of time where the target unit is no longer operational (i.e. it is busy deactivating/cleaning up/etc) but the path unit would continue to ignore inotify events. In short: any inotify event that occurs while the target unit deactivates would be completely lost. With this commit, the path will go back into a waiting state when the target unit starts deactivating. This means that any inotify event that occurs while the target unit deactivates will queue a start job.		2024-01-21 10:34:45 +00:00
..
test63-glob.path	service: set TRIGGER_UNIT= and TRIGGER_PATH= on activation by path unit	2022-08-23 20:38:08 +01:00
test63-glob.service	service: set TRIGGER_UNIT= and TRIGGER_PATH= on activation by path unit	2022-08-23 20:38:08 +01:00
test63-issue-24577-dep.service	test: add tests for "systemctl stop" vs triggering by path unit	2023-04-29 09:10:28 +09:00
test63-issue-24577.path	test: add tests for "systemctl stop" vs triggering by path unit	2023-04-29 09:10:28 +09:00
test63-issue-24577.service	test: add tests for "systemctl stop" vs triggering by path unit	2023-04-29 09:10:28 +09:00
test63-pr-30768.path	core: path: Re-enter waiting if target is deactivating	2024-01-21 10:34:45 +00:00
test63-pr-30768.service	core: path: Re-enter waiting if target is deactivating	2024-01-21 10:34:45 +00:00
test63.path	test: make TEST-63 more reliable on slower machines	2022-08-25 16:21:39 +00:00
test63.service	service: set TRIGGER_UNIT= and TRIGGER_PATH= on activation by path unit	2022-08-23 20:38:08 +01:00