On Wed, 21 Mar 2001, Thierry ITTY wrote:
> this means that a process lauched by init (in inittab) fails and is respawned
> but as the respawn cycle (due to the failure) is very short, init disables it
> have a look at inittab and see if something's wrong there
> normally only the getty's are respawned
>
> hth
>
>
>
> A 12:40 21/03/2001 -0300, vous avez écrit :
> >Hi,
> >
> >I have a DELL with linux version 2.2.14-5.0 that have RAID5 and in thew
> boot time the machine dont UP's. When I exec
> >linux single I receive:
> >
> >tryng umount old_root ok
> >INIT: canot execute " /etc/rc.d/rc.sysinit
This is an important clue! When you can not run rc.sysinit, the system
is realy messed up! Try booting using "linux init=/bin/bash" and see if
that works. If that fails, try "linux init=/bin/ash.static", or try
booting using a rescue disk system, and see what is wrong. If you do
get a prompt by using init=<shell>, then look at /etc/rc.d/rc.sysinit,
and see if you can find what is wrong with it.
> >INT: entering runlevel 3
> >INT ID " 1" respawing too fast: disabled for 5 minutes
> >INT ID " 2" respawing too fast: disabled for 5 minutes
> >INT ID " 3" respawing too fast: disabled for 5 minutes
> >INT ID " 4" respawing too fast: disabled for 5 minutes
> >INT ID " 5" respawing too fast: disabled for 5 minutes
> >INT ID " 6" respawing too fast: disabled for 5 minutes
> >INT: NO MORE PROCESS LEFT
> >
> >Can you help me?????
> >
All the mingettys are dieing. No VCs!
> >
Mikkel
--
Do not meddle in the affairs of dragons,
for you are crunchy and taste good with ketchup.
_______________________________________________
Redhat-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/redhat-list
