[systemd-bugs] [Bug 87251] sd_notify RELOADING=1 does not propagate

[bugzilla-daemon at freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=87251

dan <daniel.subs at internode.on.net> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |daniel.subs at internode.on.ne
                   |                            |t

--- Comment #1 from dan <daniel.subs at internode.on.net> ---
I saw RELOADING=1 as a notice to systemd not start new services that depend on
it until its back to READY=1.

This is just my assumption. A little more detail in
http://www.freedesktop.org/software/systemd/man/sd_notify.html may be needed.

I don't think propagating a RELOAD to further services is needed and shouldn't
be automatic. If a depending service fails I assume it will be restarted by
systemd but otherwise its up the the depending service to handle transient
failures of its dependencies.

I was planning on using this RELOADING=1 in a database that's not accepting any
changes/connections because its getting a cluster peer up to date.

To me reloading doesn't imply the IPC between this an dependent services is
going away or any stateful TCP connections will need to be remade.

Happy to consider alternate points of view or even implementation, however as
long as its documented I can deal with it.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/systemd-bugs/attachments/20150103/f6e1dcf8/attachment.html>