OpenVZ and the Ubuntu Upstart init daemon

[Kir Kolyshkin]

Scott James Remnant wrote:
> On Sun, 2007-04-08 at 15:22 +1000, Daniel Pittman wrote:
>
>   
>> The only reference to USR1 in the init code seems to be the
>> nih_signal_reset function, installing the default signal handler.
>>
>> The default for USR1, by signal(7), is to terminate the process.
>>
>>     
> No, that's not correct.  The default handling for any signal for pid #1
> is for that signal to *not be delivered*.
>
> If OpenVZ doesn't deliver signals to init correctly, then it's a bug
> there.
>
>   
>> Am I correct in my assumption -- should I take this issue of protection
>> from signals up with the OpenVZ developers so they extend the same magic
>> to the virtual PID 1 that the real PID 1 gets?
>>
>>     
> Yes, absolutely.  OpenVZ must provide the same signal handling semantics
> for pid #1 as the real kernel.  Signals (including SEGV!) are not
> delivered unless there is a non-default handler for them.
>   
Right. I have filed a bug for OpenVZ kernel:
http://bugzilla.openvz.org/533

 From the other side, I do not understand why mountall.sh script sends a 
(USR1) signal to upstart which upstart can not receive (as there's no 
handler).