From: "Richard B. Johnson" <root@chaos.analogic.com>
To: Anonymous <anon78344@yahoo.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: init dies after reboot
Date: Tue, 2 Mar 2004 11:54:29 -0500 (EST) [thread overview]
Message-ID: <Pine.LNX.4.53.0403021145150.489@chaos> (raw)
In-Reply-To: <20040302161239.79676.qmail@web20909.mail.yahoo.com>
On Tue, 2 Mar 2004, Anonymous wrote:
> Hello
>
> I encountered a strange problem, and i'm not sure that
> it originates or not in the kernel.
> the probl. is that on many slack boxes init dies after
> some time, but the OS is still up and running.
> if I 'ps aux' the machine,no init, and /proc/1 doesn't
> exist.
> although, `lsof | grep init` shows:init 1
> root cwd DIR 8,3 472 2 /
> init 1 root rtd DIR 8,3
> 472 2 /
> init 1 root txt REG 8,3
> 468916 15607 /sbin/init
> init 1 root 0r CHR 1,3
> 5659 /dev/null
> init 1 root 1u CHR 1,3
> 5659 /dev/null
> init 1 root 2u CHR 1,3
> 5659 /dev/null
> init 1 root 10u FIFO 8,3
> 137774 /dev/initctl
>
>
> Any kind of ideea?
>
> Thanks,
> Uwe Bower
The kernel will never send a signal 9 to init. However, it can
send many other signals. If the signal handler in init got
corrupt from a buffer overrun, bad memory, etc., it's quite
possible for init to die. When it dies, it would usually
die as a result of a seg-fault. You can observe /proc/1/cwd to
see where init lives. There may be a core-file in that directory.
The core-file might be able to give you a hint. Also, somebody
who has su privs can `cp /dev/random /dev/initctl` with some
interesting results.
Cheers,
Dick Johnson
Penguin : Linux version 2.4.24 on an i686 machine (797.90 BogoMips).
Note 96.31% of all statistics are fiction.
next prev parent reply other threads:[~2004-03-02 16:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-02 16:12 Anonymous
2004-03-02 16:54 ` Richard B. Johnson [this message]
2004-03-03 7:50 ` Anonymous
2004-03-03 9:00 ` Anonymous
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Pine.LNX.4.53.0403021145150.489@chaos \
--to=root@chaos.analogic.com \
--cc=anon78344@yahoo.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®