core: output unit status output strings to console, only if we actually are changing unit state

Unit _start() and _stop() implementations can fail with -EAGAIN to delay
execution temporarily. Thus, we should not output status messages before
invoking these calls, but after, and only when we know that the
invocation actually made a change.
This commit is contained in:
Lennart Poettering
2015-01-28 15:07:13 +01:00
parent 3ad85e3775
commit 82a2b6bb5e
13 changed files with 49 additions and 35 deletions
+2 -2
View File
@@ -572,7 +572,7 @@ static int path_start(Unit *u) {
p->result = PATH_SUCCESS;
path_enter_waiting(p, true, true);
return 0;
return 1;
}
static int path_stop(Unit *u) {
@@ -582,7 +582,7 @@ static int path_stop(Unit *u) {
assert(p->state == PATH_WAITING || p->state == PATH_RUNNING);
path_enter_dead(p, PATH_SUCCESS);
return 0;
return 1;
}
static int path_serialize(Unit *u, FILE *f, FDSet *fds) {