Hi,
I'm trying to use haproxy with systemd.
It cannot be done with a raw haproxy for now, because when "reloading" the
configuration file
with haproxy -sf <pid>, the former process gets killed, so the service enters a
"failed" state
and thus kills all its children, resulting in no haproxy running.
In order not to have to make a lot of modifications in the way haproxy
currently handles this,
I'm writing a wrapper around it and the corresponding systemd service file. I
will provide them
once they are fully ready. (What could be the name of this wrapper, by the way?
haproxy-systemd-wrapper?)
This requires a small modification to the haproxy entry point though: In order
to be able to track
haproxy state from the wrapper with the double fork' the entry point must not
exit after spawning
child processes.
Here is the first patch which introduces this feature.
