Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 128373 - /etc/init.d/network will not stop interfaces that have been renamed
/etc/init.d/network will not stop interfaces that have been renamed
Product: Red Hat Enterprise Linux 3
Classification: Red Hat
Component: initscripts (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Bill Nottingham
Brock Organ
Depends On:
  Show dependency treegraph
Reported: 2004-07-22 06:47 EDT by Toby Long-Leather
Modified: 2014-03-16 22:46 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2004-07-22 22:24:26 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Toby Long-Leather 2004-07-22 06:47:42 EDT
Description of problem:
The standard install uses network interface(s) that have the same
interface name and device name (e.g. interface=eth0, device=eth0).

If network interfaces have been renamed (e.g. interface=DMZNet,
device=eth0), then '/etc/init.d/network stop' will not stop the
interface.  This is because the call to check_device_down is passing
the interface name (DMZNet) rather than the device name (eth0).

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

How reproducible:

Steps to Reproduce:
1.Create a network interface with an interface name different to
device name.
2. /etc/init.d/network start
3. /etc/init.d/network stop

Additional info:
Comment 1 Bill Nottingham 2004-07-22 14:36:20 EDT
Please attach your config.
Comment 2 Toby Long-Leather 2004-07-22 19:14:57 EDT
Will attach copy of /etc/sysconfig/network-scripts/ifcfg-DMZNet next
Monday (the next time I can access the server).  The bug can be fixed
by replacing 'check_device_down $i' with 'check_device_down $DEVICE'.
Comment 3 Bill Nottingham 2004-07-22 22:24:26 EDT
This was fixed in initscripts-7.31.8.EL-1.

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