From 31afa0a44c2d7f93d837c840cdbd623982ac165f Mon Sep 17 00:00:00 2001 From: Lennart Poettering Date: Thu, 25 Apr 2013 21:57:41 -0300 Subject: unit: rework stop pending logic When a trigger unit wants to know if a stop is queued for it, we should just check precisely that and do not check whether it is actually stopped already. This is because we use these checks usually from state change calls where the state variables are not updated yet. This change splits unit_pending_inactive() into two calls unit_inactive_or_pending() and unit_stop_pending(). The former checks state and pending jobs, the latter only pending jobs. --- src/core/timer.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'src/core/timer.c') diff --git a/src/core/timer.c b/src/core/timer.c index b8039d82ec..ff8c30583c 100644 --- a/src/core/timer.c +++ b/src/core/timer.c @@ -374,7 +374,7 @@ static void timer_enter_running(Timer *t) { dbus_error_init(&error); /* Don't start job if we are supposed to go down */ - if (unit_pending_inactive(UNIT(t))) + if (unit_stop_pending(UNIT(t))) return; r = manager_add_job(UNIT(t)->manager, JOB_START, UNIT_TRIGGER(UNIT(t)), -- cgit v1.2.3