This service will be undergoing maintenance at 00:00 UTC, 2016-09-28. It is expected to last about 1 hours
Bug 84045 - hotplug's net.agent does not set IN_HOTPLUG
hotplug's net.agent does not set IN_HOTPLUG
Status: CLOSED CURRENTRELEASE
Product: Red Hat Linux
Classification: Retired
Component: hotplug (Show other bugs)
8.0
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Bill Nottingham
Brock Organ
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2003-02-11 08:49 EST by diego.santacruz
Modified: 2014-03-16 22:34 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2003-10-01 18:11:01 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:


Attachments (Terms of Use)

  None (edit)
Description diego.santacruz 2003-02-11 08:49:26 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 Galeon/1.2.6 (X11; Linux i686; U;) Gecko/20020830

Description of problem:
The net agent of hotplug, /etc/hotplug/net.agent, does not set the IN_HOTPLUG
environment variable on which the ifup script relies.

As a consequence, a net iface that is configured with HOTPLUG=no is brought up
by hotplug despite the setting.

Version-Release number of selected component (if applicable):
hotplug-2002_04_01-13, but I think it also applies to latest rawhide.

How reproducible:
Always

Steps to Reproduce:
1. Configure eth0 with HOTPLUG=no in ifcfg-eth0
2. Insert a PCMCIA network card
3.
    

Actual Results:  Hotplug system brings up the interface eth0, despite the
HOTPLUG=no setting.

Expected Results:  Hotplug sets IN_HOTPLUG variable so that ifup can honour the
HOTPLUG=no setting.

Additional info:

The IN_HOTPLUG variable was added on Aug 07 2001, but somehow it was removed
afterwards (probably after upgrading the upstream hotplug package?).
Comment 1 Bill Nottingham 2003-10-01 18:11:01 EDT
Fixed in current releases.

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