From b36996b39a4128ad9396bc0cf5ec3a57a7d31aa8 Mon Sep 17 00:00:00 2001 From: Ian Jackson Date: Tue, 16 Dec 2008 16:03:12 +0000 Subject: [PATCH] posix_aio_init: Explicitly unblock SIGUSR2 not USR1 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 --- block-raw-posix.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/block-raw-posix.c b/block-raw-posix.c index 0e1059cfa..044d1f485 100644 --- a/block-raw-posix.c +++ b/block-raw-posix.c @@ -584,7 +584,7 @@ static int posix_aio_init(void) /* 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); -- 2.39.5