Re: core dumps on signals

Albert D. Cahalan (acahalan@cs.uml.edu)
Sun, 28 Feb 1999 14:30:56 -0500 (EST)


Pavel Machek writes:

>>>> PWR n/a exit (normal systems would ignore by default)
>>>
>>> I don't think so; SIGPWR sent to init means it should shut down the
>>> system as soon as possible. If init dies, the system gets uncleanly
>>
>> Not exactly. SIGPWR is a "Power Restored" in SYS5 unix such as the NCR
>> tower. This is quite a common confusion.
>>
>> The way NCR use it for example on the old towers is that the box has
>> a battery (a big one), when the power goes off it switches to battery
>> and hibernates. This works well - we've carried machines between floors
>> without rebooting.
>
> This should be doable with linux and suspend patches. Yes, linux is
> now able to hibernate itself with suitable patches.
>
> As a side note, please DON'T recycle SIGUNUSED unless you really have
> to. Suspend patches are using it ;-).

This is another reason why it _must_ be changed. You can't support four
ports (sparc, aparc64, alpha, mips) because they don't have SIGUNUSED.

Removal of SIGUNUSED and SIGSTKFLT would reduce the temptation to
produce software that only works on half of the Linux ports.

If there is a need for more signals (I'd say yes), then SIGRTMIN
and SIGRTMAX should be adjusted. Normal UNIX systems do this.
They reserve about half of the high 32 signals for the OS.

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/