RE: init timeouts

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Thu, 10 Apr 2003, MW Mike Weiner (5028) wrote:

> From: M A Young
> No you don't. Use rpm --root /mnt/rootfs ...
>
> ahhh a good tip, thank you, as well as --dbpath i see. However thats
> currently failing,

Actually --dbpath doesn't gain you much since --root causes rpm to look
for its database in this directory as well. Also make sure glibc and
glibc-common are the same version - I know bad things happen if you manage
to get yourself in a state where they aren't.

>  and i am trying to catch the error to debug. On another
> note, is there any way around the INIT errors, when i reboot the machine
> into runlevel 5 i get:
>
> INIT: Id '1' respawning too quickly disabled for 5 minutes
> INIT: Id '2' respawning too quickly disabled for 5 minutes
> INIT: Id '3' respawning too quickly disabled for 5 minutes
> INIT: Id '4' respawning too quickly disabled for 5 minutes
> INIT: Id '5' respawning too quickly disabled for 5 minutes
> INIT: Id '6' respawning too quickly disabled for 5 minutes
> INIT: Id 'x' respawning too quickly disabled for 5 minutes
> INIT: there are no more processes in this runlevel

It sounds like init or the processes it calls are sick for some reason,
probably related to the glibc change. Incidentally, I suspect your bug is
the same as
http://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=88456

	Michael Young





[Index of Archives]     [Fedora Users]     [Centos Users]     [Kernel Development]     [Red Hat Install]     [Red Hat Watch]     [Red Hat Development]     [Red Hat Phoebe Beta]     [Yosemite Forum]     [Fedora Discussion]     [Gimp]     [Stuff]     [Yosemite News]

  Powered by Linux