(not at the office today, I hope I got the reply right nonetheless)
Miquel van Smoorenburg wrote:
>Well, it would be perfect if you could reproduce this. Try something like:
>If this prints "Caught SIGCLD" then that is a severe kernel bug.
>Try both "cc foo.c" and "cc foo.c -lpthread" please.
On 2004.12.29 16:20, Robert Waldner wrote:
On Tue, 28 Dec 2004 18:30:27 +0100, Robert Waldner writes:
>>No, kill(-1, SIGWHATEVER) is guaranteed to kill all processes
>>/except/ the caller. "man 2 kill" on any unix/linux box. What kernel
>>are you using, this might be a kernel bug. Is this an i386 o
On Tue, 28 Dec 2004 18:30:27 +0100, Robert Waldner writes:
>>No, kill(-1, SIGWHATEVER) is guaranteed to kill all processes
>>/except/ the caller. "man 2 kill" on any unix/linux box. What kernel
>>are you using, this might be a kernel bug. Is this an i386 or
>>another architecture ?
>2.4.27, from
On Tue, 28 Dec 2004 17:02:16 GMT, Miquel van Smoorenburg writes:
>> So to me it seems like "signal(SIGSTOP, SIG_IGN);" either isn't
>> honored, and killall5 itself killed, or else it kills something else
>> essential, but what could that be?
>No, kill(-1, SIGWHATEVER) is guaranteed to kill all
On 2004.12.28 17:42, Robert Waldner wrote:
On Tue, 28 Dec 2004 08:40:48 +0100, Robert Waldner writes:
>>>Hmm, can it be that killall5 doesn't actually manage to *not* kill
>>> itself?
>>Ofcourse it goes through great lengths to do exactly that - NOT
>>kill itself. It kills all processes _except_ it
On Tue, 28 Dec 2004 08:40:48 +0100, Robert Waldner writes:
>>>Hmm, can it be that killall5 doesn't actually manage to *not* kill
>>> itself?
>>Ofcourse it goes through great lengths to do exactly that - NOT
>>kill itself. It kills all processes _except_ itself and its
>>caller.
>Any hints on wha
On Mon, 27 Dec 2004 18:25:43 GMT, "Miquel van Smoorenburg" writes:
I have a HP DL380 here with Sarge (current as of now) on it. Problem
is that it's not rebooting, eg if I call `reboot` or `telinit 6`, it
starts sending out TERM and KILL signals, and everything is stopping,
In article <[EMAIL PROTECTED]>,
Robert Waldner <[EMAIL PROTECTED]> wrote:
>On Mon, 27 Dec 2004 12:25:08 +0100, John Smith writes:
>>On Mon, 2004-12-27 at 10:48 +0100, Robert Waldner wrote:
>>> I have a HP DL380 here with Sarge (current as of now) on it. Problem
>
>> It must be one of the most men
On Mon, 27 Dec 2004 12:25:08 +0100, John Smith writes:
>On Mon, 2004-12-27 at 10:48 +0100, Robert Waldner wrote:
>> I have a HP DL380 here with Sarge (current as of now) on it. Problem
> It must be one of the most mentioned boxes on these lists, a
>distinction I wouldn't crave, as it's manufactu
On Mon, 2004-12-27 at 10:48 +0100, Robert Waldner wrote:
> I have a HP DL380 here with Sarge (current as of now) on it. Problem
It must be one of the most mentioned boxes on these lists, a
distinction I wouldn't crave, as it's manufacturer... (Hey, HP, are you
listening? You are using Debian inh
Hi!
I have a HP DL380 here with Sarge (current as of now) on it. Problem
is that it's not rebooting, eg if I call `reboot` or `telinit 6`, it
starts sending out TERM and KILL signals, and everything is stopping,
up to and including klogd and syslogd. Then, instead of writing
"Rebooting...
11 matches
Mail list logo