Re: [Sheflug] Oh gloom

["Chris J" <xxxxx [at] xxxxxxxxxxxx>]

>
> INT: Id "1" respawning too fast; disabled for 5 minutes
> INT: Id "2" respawning too fast; disabled for 5 minutes
> INT: Id "3" respawning too fast; disabled for 5 minutes
> INT: Id "4" respawning too fast; disabled for 5 minutes
> INT: Id "5" respawning too fast; disabled for 5 minutes
> INT: Id "6" respawning too fast; disabled for 5 minutes
> INIT: No more processes left in this runlevel
>

Okay, what this means is that the processes started by inittab, whose id's
are 1,2,3,4,5,6 are "respawning too fast" - in other words, its trying to
start the process and the process is probably dying almost immediately. When
it dies, inittab will respawn the process. If it happens too quickly, init
will disable the offending process so it doesn't chew up system resources.

Now I'd assume (don't have a SuSE box available) that what is failing is the
getty's for the VTs (be it agetty, getty, mgetty, vgetty ... what does SuSE
use?). So what you'll have to do is boot to single user mode, check that
inittab is sane, then look to see why *getty fails to start.

First try an ldd on the getty binary, and ensure the libraries are correct.
If not, you'll need to find the missing libraries and install them. If
they're correct, check permissions on the getty binary.

If all seems okay, send /etc/inittab here so we can have a closer look. The
results of an ldd check of the getty binary may also be useful.

Chris...

-- 
\ Chris Johnson                 \
 \ cej [at] nightwolf.org.uk          \
  \ http://cej.nightwolf.org.uk/  ~-----------------------------------+
   \ Redclaw chat - http://redclaw.org.uk - telnet redclaw.org.uk 2000 \____



___________________________________________________________________

Sheffield Linux User's Group - http://www.sheflug.co.uk . 
To unsubscribe from this list send mail to 
shef-lug-request@list.sheflug.org.uk with the word
"unsubscribe" in the body of the message. 

  GNU the choice of a complete generation.