summaryrefslogtreecommitdiff
path: root/src/core/manager.h
diff options
context:
space:
mode:
authorLennart Poettering <lennart@poettering.net>2013-07-10 21:10:53 +0200
committerLennart Poettering <lennart@poettering.net>2013-07-10 23:41:03 +0200
commit71445ae75b0e9954d141e5f0ee97803b406ea332 (patch)
treef1f00a625f725d72429c51d61eb24b3842bd2648 /src/core/manager.h
parentd0ede8f1c555500dceebd3cc8a8e877ed1d89de6 (diff)
core: send out "Reloading" signal before and after doing a full reload/reexec of PID 1
Since we'll unload all units/job during a reload, and then readd them it is really useful for clients to be aware of this phase hence sent a signal out before and after. This signal is called "Reloading" (despite the fact that it is also sent out during reexecution, which we consider a special case in this context) and has one boolean parameter which is true for the signal sent before the reload, and false for the signal after the reload. The UnitRemoved/JobRremoved and UnitNew/JobNew due to the reloading are guranteed to be between the pair of Reloading messages.
Diffstat (limited to 'src/core/manager.h')
-rw-r--r--src/core/manager.h2
1 files changed, 2 insertions, 0 deletions
diff --git a/src/core/manager.h b/src/core/manager.h
index 31da04e47c..6d5241497d 100644
--- a/src/core/manager.h
+++ b/src/core/manager.h
@@ -195,6 +195,8 @@ struct Manager {
int32_t conn_data_slot;
int32_t subscribed_data_slot;
+ bool send_reloading_done;
+
uint32_t current_job_id;
uint32_t default_unit_job_id;