From 82a2b6bb5e4e5d294f09af778c48974a7857afb6 Mon Sep 17 00:00:00 2001 From: Lennart Poettering Date: Wed, 28 Jan 2015 15:07:13 +0100 Subject: 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. --- src/core/busname.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'src/core/busname.c') diff --git a/src/core/busname.c b/src/core/busname.c index 00e56686e5..ca9ceb8c3c 100644 --- a/src/core/busname.c +++ b/src/core/busname.c @@ -615,7 +615,7 @@ static int busname_start(Unit *u) { n->result = BUSNAME_SUCCESS; busname_enter_making(n); - return 0; + return 1; } static int busname_stop(Unit *u) { @@ -638,7 +638,7 @@ static int busname_stop(Unit *u) { assert(IN_SET(n->state, BUSNAME_REGISTERED, BUSNAME_LISTENING, BUSNAME_RUNNING)); busname_enter_dead(n, BUSNAME_SUCCESS); - return 0; + return 1; } static int busname_serialize(Unit *u, FILE *f, FDSet *fds) { -- cgit v1.2.3-54-g00ecf