diff options
| author | Lennart Poettering <lennart@poettering.net> | 2013-07-10 21:10:53 +0200 |
|---|---|---|
| committer | Lennart Poettering <lennart@poettering.net> | 2013-07-10 23:41:03 +0200 |
| commit | 71445ae75b0e9954d141e5f0ee97803b406ea332 (patch) | |
| tree | f1f00a625f725d72429c51d61eb24b3842bd2648 /test/f.service | |
| parent | d0ede8f1c555500dceebd3cc8a8e877ed1d89de6 (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 'test/f.service')
0 files changed, 0 insertions, 0 deletions