Bug 15285 – ifdown-local executed twice

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 15285 - ifdown-local executed twice

Summary:	ifdown-local executed twice

Status:	CLOSED RAWHIDE

Aliases:	None

Product:	Red Hat Linux
Classification:	Retired
Component:	initscripts (Show other bugs)
Sub Component:
Version:	7.0
Hardware:	i386 Linux

Priority	medium Severity medium
Target Milestone:	---
Target Release:	---
Assigned To:	Bill Nottingham
QA Contact:
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2000-08-03 15:16 EDT by Andrea Borgia
Modified:	2014-03-16 22:15 EDT (History)
CC List:	1 user (show)

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2000-08-18 01:56:28 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)
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description Andrea Borgia 2000-08-03 15:16:40 EDT

/sbin/ifdown calls
/usr/sbin/usernetctl down (if uid!=0) that calls
/sbin/ifdown that calls
/etc/sysconfig/network-scripts/ifdown-ppp that calls
/etc/sysconfig/network-scripts/ifdown-post that finally calls
/sbin/ifdown-local

also, /etc/ppp/ip-down calls
/etc/sysconfig/network-scripts/ifdown-post that calls
/sbin/ifdown-local

Et voila! ifdown-local ends up being called twice. I found out because both named
wwwoffle complain about duplicate commands (already stopped or already offline).

I found this:
# killing ppp-watch twice in a row causes it to send a SIGKILL to pppd pgrp
kill -TERM $PID > /dev/null 2>&1
# ip-down won't run in this case

Maybe this no longer holds true?

*** Perhaps this no longer holds true? (6.2, initscripts 5.00-1)

Comment 1 Andrea Borgia 2000-08-11 02:39:19 EDT

Still present in Pinstripe

Comment 2 borgia 2000-08-18 01:56:26 EDT

Still present in RC1

Comment 3 Bill Nottingham 2000-08-18 17:38:38 EDT

will be fixed in 5.46-1.

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