Bug 88709 - Update glibc-2.3.2-27.9 on Red Hat version 9 causes INIT problem
Update glibc-2.3.2-27.9 on Red Hat version 9 causes INIT problem
Status: CLOSED DUPLICATE of bug 88456
Product: Red Hat Linux
Classification: Retired
Component: glibc (Show other bugs)
9
i386 Linux
high Severity high
: ---
: ---
Assigned To: Jakub Jelinek
Brian Brock
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2003-04-12 00:56 EDT by Tjaun
Modified: 2006-02-21 13:52 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2006-02-21 13:52:38 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:


Attachments (Terms of Use)

  None (edit)
Description Tjaun 2003-04-12 00:56:47 EDT
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; .NET CLR 
1.0.3705)

Description of problem:
Bad: I just installed my RH9. Then I upgrade my glibc using rpm -Fvh. During 
the upgrade, I encounter problem with it by having segmentation fault on some 
script stuff I remember. From there on I could not input anything at all and I 
got to reset the system. Upon rebooting, the boot-up process hangs and produce 
the following error: Init respawning too fast: disabled for 5 minutes on each 
mingetty ID. I could not boot to reach the login screen. By the way, my 
mingetty is configured with only 3 of it rather then 6 of it just to save some 
memory.

To be more precise on the error during the boot-up process here is what shown:

INIT: Id "x" respawning too fast : disabled for 5 minutes

x = mingetty 1,2,3,4,5,6


Version-Release number of selected component (if applicable):
glibc-2.3.2-27.9

How reproducible:
Didn't try


Additional info:

I installed numerous related glibc together during the installation. Which 
means I did a rpm -Fvh glibc-2.3.2-27.9.i386.rpm glibc-devel-2.3.2-
27.9.i386.rpm glibc-debug-2.3.2-27.9.i386.rpm in the command.
Comment 1 Jakub Jelinek 2003-04-12 04:29:37 EDT

*** This bug has been marked as a duplicate of 88456 ***
Comment 2 Red Hat Bugzilla 2006-02-21 13:52:38 EST
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.

Note You need to log in before you can comment on or make changes to this bug.