Bug 88353 - network rc.d script should look harder for devices to start
network rc.d script should look harder for devices to start
Status: CLOSED NOTABUG
Product: Red Hat Linux
Classification: Retired
Component: initscripts (Show other bugs)
9
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Bill Nottingham
Brock Organ
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2003-04-09 07:18 EDT by Michael Young
Modified: 2014-03-16 22:35 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2003-06-23 12:17:39 EDT
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 Michael Young 2003-04-09 07:18:18 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; SunOS sun4u; en-US; rv:1.0.1) Gecko/20020921
Netscape/7.0

Description of problem:
The network script in /etc/rc.d/init.d gets the list of devices to try to start
from /etc/sysconfig/network-scripts. However the ifup script that actually
starts the device looks in other places first (as in bug 82246 ). This means
that for every device you want started automatically, there has to be a file
such as ifcfg-eth0 in /etc/sysconfig/network-scripts even if this file isn't
actually used to configure the device, which at the least is highly confusing
behaviour.
What should happen is that the network script should look for interfaces in the
same places as ifup, and in the same order.
Comment 1 Bill Nottingham 2003-06-23 12:17:39 EDT
Actually, the excessive searching in ifup was removed, so they match again now.

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