Date: Thu, 07 May 2009 11:03:44 +0300 From: Andriy Gapon <avg@icyb.net.ua> To: peterjeremy@optushome.com.au Cc: freebsd-arch@freebsd.org Subject: Re: shutdown_nice during boot Message-ID: <4A0295E0.4020609@icyb.net.ua> In-Reply-To: <20090507080048.GA64648@server.vk2pj.dyndns.org> References: <4A01B9A3.2030806@icyb.net.ua> <20090507080048.GA64648@server.vk2pj.dyndns.org>
next in thread | previous in thread | raw e-mail | index | archive | help
on 07/05/2009 11:00 peterjeremy@optushome.com.au said the following: > On 2009-May-06 19:24:03 +0300, Andriy Gapon <avg@icyb.net.ua> wrote: >> It's possible to re-enable SIGINT right after init is forked, but >> this way it will be delivered to init before it installs signal >> handlers and thus init would simply terminate resulting in "Going >> nowhere without my init!" panic. > > The best option would seem to be for init(8) to call sigprocmask(2) > immediately it starts up and block all signals. But a signal still can be delivered after init is exec-ed and before sigprocmask(2) is called or not? > This causes signals > to be deferred until they are unblocked. Once it sorts out its signal > handlers, it can then unblock the signals - at which point it will > receive any signals that were sent in the interim. > > Note that I haven't looked into init(8) to see if there are other > reasons why this approach would not be appropriate > -- Andriy Gapon
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4A0295E0.4020609>