I started tinkering with haproxy-systemd-wrapper recently and noticed
that I get two haproxy processes when I start:

# systemctl start haproxy
# systemctl status haproxy
haproxy.service - HAProxy Load Balancer
   Loaded: loaded (/usr/lib/systemd/system/haproxy.service; disabled)
   Active: active (running) since Sat 2014-02-15 10:39:20 CST; 1s ago
 Main PID: 10065 (haproxy-systemd)
   CGroup: /system.slice/haproxy.service
           ├─10065 /usr/sbin/haproxy-systemd-wrapper -f
           /etc/haproxy/haproxy.cfg -p /run/haproxy....
           ├─10066 /usr/sbin/haproxy -f /etc/haproxy/haproxy.cfg -p
           /run/haproxy.pid -Ds
           └─10067 /usr/sbin/haproxy -f /etc/haproxy/haproxy.cfg -p
           /run/haproxy.pid -Ds

That doesn't seem right. A quick look the haproxy processes shows an
interesting parent/child relationship:

# ps -C haproxy -o pid,ppid
  PID  PPID
10066 10065
10067 10066

Can someone explain what is going on here? I'm using 1.5-dev22 and the
systemd service file from the source.

Thanks.
Ryan

Reply via email to