Bug 326 - Missing file halts network startup procedure
Summary: Missing file halts network startup procedure
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: linuxconf
Version: 5.2
Hardware: i386
OS: Linux
Target Milestone: ---
Assignee: David Lawrence
QA Contact:
Depends On:
TreeView+ depends on / blocked
Reported: 1998-12-07 12:17 UTC by verm
Modified: 2017-07-25 13:41 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 1998-12-09 19:44:39 UTC

Attachments (Terms of Use)

Description verm 1998-12-07 12:17:22 UTC
When the file /etc/redhat-release is missing, the network
startup procedure will halt on a script called
No error message is given.
The problem is that the program linuxconf, which is called
in this script, needs this file. When
	linuxconf --hint routing "$1"
is started manually, it gives an error message.
I solved the problem by recreating the file redhat-release.
However, there seems to be no necessity for linuxconf to
halt on the nonexistence of this file, so doing so should be
seen as a bug in linuxconf.

Comment 1 Jay Turner 1998-12-08 22:06:59 UTC
Yes, if the redhat-release file is missing, then the startup of
linuxconf will indeed fail.  Unable to replicate this file not getting
created however.  Need more information about the circumstances
surrounding this error, i.e. which type of install are you doing,
where in the install is the problem occurring?

Comment 2 David Lawrence 1998-12-09 19:44:59 UTC
Linuxconf does indeed fail if the redhat-release file is missing, and
this is as a result of the dependance of Linuxconf on the file.  This
is by design.  Let us know if there are situations where the
redhat-release file is not getting created.

Comment 3 openshift-github-bot 2017-07-25 13:41:49 UTC
Commits pushed to master at https://github.com/openshift/openshift-sdn

Fix debug.sh error when it is executed on containerized cluster (issue #326)

Merge pull request #327 from harobed/issue326

Fix debug.sh error when it is executed on containerized cluster

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