On Sun, Feb 16, 2014 at 11:12:03AM +0900, Marc-Antoine Perennou wrote: > 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.
Yes. That is precisely what I was thinking. Thanks again. Ryan
