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 84453 - ifdown-post not called when pccard ethernet ejected (from ifdown)
ifdown-post not called when pccard ethernet ejected (from ifdown)
Status: CLOSED DUPLICATE of bug 127283
Product: Red Hat Linux
Classification: Retired
Component: hotplug (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Bill Nottingham
Brock Organ
Depends On:
  Show dependency treegraph
Reported: 2003-02-17 11:50 EST by John Heidemann
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:
Last Closed: 2006-02-21 13:51:50 EST
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 John Heidemann 2003-02-17 11:50:35 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.3b) Gecko/20030211

Description of problem:
ifdown-post is never called at the end of ifdown
if retcode != 0.
This happens to me consistently when ejecting a pccard ethernet
As a result, jobs registered in /var/run/netreport
never get informed that the network went away.
This breaks third-party apps such as xcron
that require notification.

(At some previous point ejecting a pccard did trigger netreports.
I'm not sure when: RH 7.3?  7.2?  The code in 7.3 looks the same, but 
maybe the retcode ends up being set differently.)

Presumably this is done because of ungraceful shutdown.  Perhaps
ifdown-post should try and pass the retcode down.

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

How reproducible:

Steps to Reproduce:
1. start a process that registers itself in /var/run/netreport
   on a laptop
2. physically eject the card
3. observe that no SIGIO is delivered to the process

Actual Results:  a SIGIO is not delivered to the process registered in

Expected Results:  a SIGIO should have been delivred to the process

Additional info:
Comment 1 Bill Nottingham 2003-09-03 21:45:01 EDT
This is because of the switch to hotplug for handling network devices with
Comment 2 Bill Nottingham 2005-02-04 16:08:16 EST

*** This bug has been marked as a duplicate of 127283 ***
Comment 3 Red Hat Bugzilla 2006-02-21 13:51:50 EST
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.

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