On Sat, 2014-02-15 at 20:04 -0600, Ryan O'Hara wrote: > On Sun, Feb 16, 2014 at 10:08:31AM +0900, Marc-Antoine Perennou wrote: > > > This is why you get > > > > haproxy-systemd-wrapper -> main haproxy process -> haproxy worker. > > > > haproxy-systemd-wrapper waits for the main haproxy process to exit to > > avoir zombies. The main haproxy process exits when all its workers are > > done. > > It has been while since I dealt with this, but can't you double fork > to avoid zombies? Is it a double fork that causes problems for systemd? >
Double forking would work fine, but the wrapper wouldn't be linked to the worker processes and thus couldn't check whether there has been a problem or not. Without the double fork, if there is a problem, the wrapper will exit and you'll be able to notice it. With the double fork, we would end up with some kind of endless loop instead of a waiting loop, and it would never exit. > > > Thanks. > > > Ryan > > > > > > > Hope that helps and sounds right. > > > > Marc-Antoine > > It does help. Thank you. > > Ryan > Regards Marc-Antoine
