Bug 121126 - (hwdata?) "Too many open files" from initscripts
(hwdata?) "Too many open files" from initscripts
Status: CLOSED DUPLICATE of bug 121106
Product: Fedora
Classification: Fedora
Component: hwdata (Show other bugs)
rawhide
All Linux
medium Severity medium
: ---
: ---
Assigned To: Bill Nottingham
Brock Organ
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2004-04-17 13:56 EDT by Michal Jaegermann
Modified: 2014-03-16 22:44 EDT (History)
2 users (show)

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


Attachments (Terms of Use)

  None (edit)
Description Michal Jaegermann 2004-04-17 13:56:49 EDT
Description of problem:

When starting a machine, at least with 2.6.5-1.326smp kernel,
I am consistenly getting:

Checking for new hardware                                  [  OK  ]
Updating /etc/fstab error opening /etc/updfstab.conf.default: Too many
open files
                                                           [FAILED]

In case you wonder at this moment I have 'selinux=0'.

Version-Release number of selected component (if applicable):
initscripts-7.50-1

How reproducible:
Always.
Comment 1 Warren Togami 2004-04-18 14:52:18 EDT
I believe this has been corrected in hwdata-0.117-1.  Please check
your version and report back.
Comment 2 Michal Jaegermann 2004-04-18 17:03:58 EDT
After recent bunch of updates which included hwdata-0.117-1
this error indeed disappeared.
Comment 3 Warren Togami 2004-04-18 19:31:25 EDT
Keeping this open for a little while so others see it when they search
for open bugs.
Comment 4 Bill Nottingham 2004-04-19 00:45:00 EDT

*** This bug has been marked as a duplicate of 121106 ***
Comment 5 Red Hat Bugzilla 2006-02-21 14:02:39 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.