Bug 78992 - Alias interfaces can't be disabled
Alias interfaces can't be disabled
Product: Red Hat Linux
Classification: Retired
Component: initscripts (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Bill Nottingham
Brock Organ
: FutureFeature
Depends On:
  Show dependency treegraph
Reported: 2002-12-04 09:12 EST by Jos Vos
Modified: 2014-03-16 22:32 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2003-01-13 23:35:52 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
Patch against 6.90-1 (790 bytes, patch)
2003-01-14 04:22 EST, Jos Vos
no flags Details | Diff

  None (edit)
Description Jos Vos 2002-12-04 09:12:05 EST
Description of Problem:
The alias interface configuration (e.g., ifcfg-eth0:0) doesn't support a feature
to disable it.  Even if ONBOOT=no, the alias interface will be brought up
together with the parent interface.  This causes a problem in case someone wants
to control the alias interface only manually, with explicit "ifup" and "ifdown"

Version-Release number of selected component (if applicable):
All initscripts versions, up to 6.90-1.

Additional Information:
I will attach a (backwards-compatible) patch to solve this problem. If
ONPARENT=no is set in the config file, the interface will not be brought up
automatically together with the parent.
Comment 1 Bill Nottingham 2003-01-13 23:29:52 EST
Comment 2 Bill Nottingham 2003-01-13 23:35:52 EST
but something added in 7.03-1 anyway. :)
Comment 3 Jos Vos 2003-01-14 04:22:12 EST
Created attachment 89344 [details]
Patch against 6.90-1

Sorry, I seem to have forgotten to attach the patch earlier.  This is my patch,
don't know how this compares to your solution.
Comment 4 Bill Nottingham 2003-01-14 12:58:14 EST
Similar, although I note I missed the second case, which will be fixed in 7.04-1.

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