Files
systemd/src/core
Jonathon Kowalski 791cd15993 Fail RequisiteOf units with oneshots
Fixes: #11422

Oneshots going to inactive directly without ever entering UNIT_ACTIVE is
considered success. This however means that if something both Requires=
and Requisites= a unit of such nature, the verify-active job getting
merged into the start job makes it lose this property of failing the
depending jobs, as there, the start job has the result JOB_DONE on
success, so we never walk over RequisiteOf units.

This change makes sure that such units always go down. It is also only
meaningful with After=, but so is Requisite= itself. Also, we also catch
cases like a oneshot having RemainAfterExit= true making us start up
properly in such a setting, but then removing it, reloading the unit,
and restarting it. In such a case, we go down due to restart propagation
before them, and our start job waits on theirs, properly failing with
the JOB_DEPENDENCY result.

This covers cases where ConditionXYZ= creates a similar situation as
well.
2019-02-15 13:42:54 +01:00
..
2019-01-12 16:02:26 +01:00
2018-06-29 11:02:17 +09:00
2019-02-14 11:04:42 -08:00
2018-09-26 16:14:29 +02:00
2019-01-17 16:12:38 +01:00
2019-01-22 14:51:02 +09:00
2019-02-15 13:42:54 +01:00
2018-12-12 11:15:07 +01:00
2018-09-26 16:14:29 +02:00
2018-09-26 16:14:29 +02:00
2018-09-25 12:50:35 +02:00
2019-02-14 11:04:42 -08:00
2018-08-23 04:57:39 +09:00
2018-06-14 13:03:20 +02:00
…