[ale] Uh-oh. too many processes at boot

[Chris Fowler]

I would look ar rc.sysinit then.  I doubt init would respawn too many
processes if inittab looks normal.
Yuo may see a respawning too fast error message.  But it appears that maybe
the upgrade has mucked up
your startup scripts.  I never upgrade.  There is just too many things that
could go wrong.  Especiailly if
you are like me and remove almost everything from /etc/rc3.d.

Chris


-----Original Message-----
From: David Corbin [mailto:dcorbin at imperitek.com]
To: ale at ale.org
Sent: Sunday, April 14, 2002 9:01 PM
To: Chris Fowler
Subject: Re: [ale] Uh-oh. too many processes at boot


I've looked at it, it looks normal to me.  There's nothing wrong with it
as far as I can tell.  It's more like something something else is
spawning too many process, and the init spawns one and its overloaded.
Is there anyway to log *all* spawned processes? I wouldn't think so, but
I figured I'd ask.

Chris Fowler wrote:

>I would take a good inittab.  Like I have attached and use it as a
>reference.  Use vi to edit your old one.
>
>
>
>
>-----Original Message-----
>From: David Corbin [mailto:dcorbin at imperitek.com]
>Sent: Sunday, April 14, 2002 6:14 PM
>To: Cfowler
>Cc: ale at ale.org
>Subject: Re: [ale] Uh-oh. too many processes at boot
>
>
>Because I know you're generally active here, I was thinking you might
>have missed my follow up question.
>
>What changes do I make to inittab?
>
>Cfowler wrote:
>
>>lilo:  linux single
>>
>>
>>Init will  give you a # prompt so you can fix.
>>You'll need to edit your /etc/inittab but the filessytem is mounted
>>read-only.
>>
>>Fix:
>>
>># mount / -o rw,remount
>># vi /etc/inittab
>># sync
>># mount / -o ro,remount
>># reboot
>>
>>You are done!
>>
>>--------- Original message --------
>>From: "David Corbin" <dcorbin at imperitek.com>
>>To: "ale at ale.org" <ale at ale.org>
>>Subject: [ale] Uh-oh. too many processes at boot
>>Date: 04-12-02 12:01
>>
>>I have debian system. I upgrade to the debian test (at the time, I
>>thought I need and more recent ssh). I had my system lock up. During
>>reboot, it took a lot of effort to successfully get through the FSCK.
>>But, I have.
>>
>>Now, when I boot to runlevel 2 (the default), I end-up with "INIT: too
>>many processes for this run level". But, if I boot to run-level 1, and
>>then manually run the various S scripts in /etc/rc2.d, I don't have a
>>problem.
>>
>>1) I don't know if I've got an upgrade problem, or a loss do to "hard
>>shutdown". Ideas?
>>2) How do I figure out what's doing all the spawning?
>>
>>Thanks.
>>David
>>
>>
>>---
>>This message has been sent through the ALE general discussion list.
>>See http://www.ale.org/mailing-lists.shtml for more info. Problems should
>>
>be
>
>>sent to listmaster at ale dot org.
>>
>
>
>
>
>---
>This message has been sent through the ALE general discussion list.
>See http://www.ale.org/mailing-lists.shtml for more info. Problems should
be
>sent to listmaster at ale dot org.
>
>






---
This message has been sent through the ALE general discussion list.
See http://www.ale.org/mailing-lists.shtml for more info. Problems should be 
sent to listmaster at ale dot org.