Couple of questions related to the systemd wrapper:

1) I noticed that it spawns a 2 level hierarchy of haproxy processes
instead of a single child process. Can someone help understand why?

2) The problem arises when the intermediate haproxy process dies for any
reason and the child process is adopted by pid 1. When the systemd wrapper
is restarted, this results in a total of 3 haproxy processes. Is this
behavior expected? Are there fixes/workaround to ensure that only
systemd-wrapper controlled processes are retained?

Thanks,
Bharath

Reply via email to