> Same for all of them. Very interesting, SIGUSR2 (12) is set > in SigIgn :-) One question is "why", but at least we know we > have a workaround consisiting in unblocking these signals in > haproxy-systemd-wrapper, as we did in haproxy.
> Care to retry with the attached patch ? Same behaviour. SigIgn is still 0000000000001000 (which is probably normal, I assume the goal was to ignore that). Pierre
