Date: Sat, 15 Jan 2011 08:18:58 +0000 (UTC) From: Pawel Jakub Dawidek <pjd@FreeBSD.org> To: cvs-src-old@freebsd.org Subject: cvs commit: src/sbin/hastd hastd.c hooks.c Message-ID: <201101150819.p0F8JJFM034805@repoman.freebsd.org>
next in thread | raw e-mail | index | archive | help
pjd 2011-01-15 08:18:58 UTC FreeBSD src repository Modified files: (Branch: RELENG_8) sbin/hastd hastd.c hooks.c Log: SVN rev 217439 on 2011-01-15 08:18:58Z by pjd MFC r217307,r217308,r217312: r217307: Install default signal handlers before masking signals we want to handle. It is possible that the parent process ignores some of them and sigtimedwait() will never see them, eventhough they are masked. The most common situation for this to happen is boot process where init(8) ignores SIGHUP before starting to execute /etc/rc. This in turn caused hastd(8) to ignore SIGHUP. Reported by: trasz Obtained from: Wheel Systems Sp. z o.o. http://www.wheelsystems.com r217308: Add a note that when custom signal handler is installed for a signal, signal action is restored to default in child after fork(2). In this case there is no need to do anything with dummy SIGCHLD handler, because after fork(2) it will be automatically reverted to SIG_IGN. Obtained from: Wheel Systems Sp. z o.o. http://www.wheelsystems.com r217312: execve(2), not fork(2) resets signal handler to the default value (if it isn't ignored). Correct comment talking about that. Pointed out by: kib Revision Changes Path 1.2.2.10 +8 -0 src/sbin/hastd/hastd.c 1.1.2.6 +5 -0 src/sbin/hastd/hooks.c
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201101150819.p0F8JJFM034805>