In
1f4f23ae9fc220eec55aa742f67f5bb47716bcc6 I arranged to explicitly
unblock the wrong signal - the occurrence of SIGUSR1 was a leftover
from my various debugging trees.
Signed-off-by: Ian Jackson <ian.jackson@eu.citrix.com>
/* under some circumstances on Centos 4.3 (at least)
* SIGUSR2 is mistakenly blocked, which breaks badly */
sigemptyset(&enable);
- sigaddset(&enable,SIGUSR1);
+ sigaddset(&enable,SIGUSR2);
sigprocmask(SIG_UNBLOCK,&enable,0);
sigfillset(&act.sa_mask);