From mboxrd@z Thu Jan 1 00:00:00 1970 From: Dave Hansen Subject: Re: [PATCH] Signal semantics for /sbin/init Date: Tue, 30 Oct 2007 10:30:32 -0700 Message-ID: <1193765432.24087.280.camel@localhost> References: <20071027190010.GA10397@us.ibm.com> Mime-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: containers-bounces-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org Errors-To: containers-bounces-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org To: "Eric W. Biederman" Cc: Containers , clg-NmTC/0ZBporQT0dZR+AlfA@public.gmane.org, Oleg Nesterov , Pavel Emelianov List-Id: containers.vger.kernel.org On Mon, 2007-10-29 at 19:24 -0600, Eric W. Biederman wrote: > > When sending a signal to init. The presence of a signal handler > that is neither SIG_IGN nor SIG_DFL allows the signal to be sent to > init. If the signal is not sent it is silently dropped, without > becoming pending. Further if init specifies it's signal handler as > SIG_IGN or SIG_DFL all pending signals will be dropped. Does this mean that container-init processes are specially treated when signalled from _outside_ the container for which they are the init? -- Dave