diff options
author | Lennart Poettering <lennart@poettering.net> | 2013-03-23 03:16:17 +0100 |
---|---|---|
committer | Lennart Poettering <lennart@poettering.net> | 2013-03-23 03:16:17 +0100 |
commit | 335b5240ae584ed184afc683519bf19d6e1e1145 (patch) | |
tree | 639829540997c29e82c7ff5c0c44093616fe19fb | |
parent | 0debd2bf2f92d4e8f7a3e520c6c1d522e5058929 (diff) |
unit: never retroactively start requisites
Requesites are not supposed to be auto-started afterall, they are just
checks, so don't try to be smarter here than appropriate.
Based on a patch from Michal Schmidt.
-rw-r--r-- | src/core/unit.c | 5 |
1 files changed, 0 insertions, 5 deletions
diff --git a/src/core/unit.c b/src/core/unit.c index d43558e6df..711167994a 100644 --- a/src/core/unit.c +++ b/src/core/unit.c @@ -1241,11 +1241,6 @@ static void retroactively_start_dependencies(Unit *u) { !UNIT_IS_ACTIVE_OR_ACTIVATING(unit_active_state(other))) manager_add_job(u->manager, JOB_START, other, JOB_FAIL, false, NULL, NULL); - SET_FOREACH(other, u->dependencies[UNIT_REQUISITE], i) - if (!set_get(u->dependencies[UNIT_AFTER], other) && - !UNIT_IS_ACTIVE_OR_ACTIVATING(unit_active_state(other))) - manager_add_job(u->manager, JOB_START, other, JOB_REPLACE, true, NULL, NULL); - SET_FOREACH(other, u->dependencies[UNIT_WANTS], i) if (!set_get(u->dependencies[UNIT_AFTER], other) && !UNIT_IS_ACTIVE_OR_ACTIVATING(unit_active_state(other))) |