Hi Jarno, On Tue, Oct 25, 2016 at 11:43:44AM +0300, Jarno Huuskonen wrote: > This is probably a bit off topic, but there's sd_notify call > (and [Service] Type=notify) > where service can notify systemd that it's done starting/reloading > configuration: > https://www.freedesktop.org/software/systemd/man/sd_notify.html
Thank you, that can be useful for future improvements on the wrapper. And no, it's not off-topic, quite the opposite. > I don't know if systemd-wrapper would call: > sd_notify(0, "RELOADING=1"); > ... restart > sd_notify(0, "READY=1"); > if this would prevent systemd from trying to do multiple reloads before > haproxy has finished starting. Yes, however for now the problem is that the wrapper doesn't even know whether or not haproxy has finished restarting since it stays attached. I'm starting to think that the wrapper was a good idea to address short term incompatibilities, but over the long term we may have to think again about a master-worker architecture that would address this. And this combined with previous Simon's work on the socket server could possibly also help address the RST on close issue. Thanks, willy
