On Sat, Feb 09, 2013 at 11:45:57AM +0100, Marc-Antoine Perennou wrote: > Maybe this can help you understand why it works: > > Before the download: > haproxy 6090 root 4u IPv4 53819 0t0 TCP > *:http (LISTEN) > haproxy 6092 root 4u IPv4 53819 0t0 TCP > *:http (LISTEN) > haproxy 6093 root 4u IPv4 53819 0t0 TCP > *:http (LISTEN) > > During the download: > haproxy 6090 root 4u IPv4 53819 0t0 TCP > *:http (LISTEN) > haproxy 6092 root 4u IPv4 53819 0t0 TCP > *:http (LISTEN) > haproxy 6093 root 1u IPv4 57972 0t0 TCP > Lou.local:http->Lou.local:40395 (ESTABLISHED) > haproxy 6093 root 4u IPv4 53819 0t0 TCP > *:http (LISTEN) > > During the download, after the reload: > haproxy 6093 root 1u IPv4 57972 0t0 TCP > Lou.local:http->Lou.local:40395 (ESTABLISHED) > haproxy 6239 root 4u IPv4 54622 0t0 TCP > *:http (LISTEN) > haproxy 6240 root 4u IPv4 54622 0t0 TCP > *:http (LISTEN) > haproxy 6241 root 4u IPv4 54622 0t0 TCP > *:http (LISTEN)
OK so the old parent process got the signal and left the place. I don't know why, but I thought that the pidfile only contained the children pids, but here it's clear that the parent got the signal as well. That's fine then. Thanks, Willy
