Bug 136152

Summary: ifdown script leaves dhcpcd running if BOOTPROTO changed while interface is up
Product: Red Hat Enterprise Linux 2.1 Reporter: Neil Horman <nhorman>
Component: initscriptsAssignee: Bill Nottingham <notting>
Status: CLOSED DUPLICATE QA Contact: Brock Organ <borgan>
Severity: medium Docs Contact:
Priority: medium    
Version: 2.1CC: rvokal, tao
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2006-02-21 19:06:24 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---
Description Flags
patch to kill appropriate dhcpcd|pump client after iface config has changed none

Description Neil Horman 2004-10-18 12:16:40 UTC
Description of problem:
If an interface is ifup-ed with a config indicating
BOOTPROTO=[dhcp|bootp], and then the config is changed such that
BOOTPROTO=static, the dhcpcd or pump daemon is left running when
service network restart is run, leading to undesired interface address

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

How reproducible:

Steps to Reproduce:
1.config an interface to use dhcp or bootp
2.start the interface with service network restart or ifup
3.reconfig the interface such that BOOTPROTO=static
4.restart networking service
Actual results:
dhcpcd|pump is left running, and eventually the ip address will change
on the interface when the lease is renewed

Expected results:
dhcpcd|pump should be killed

Additional info:

Comment 1 Neil Horman 2004-10-18 12:17:32 UTC
Created attachment 105372 [details]
patch to kill appropriate dhcpcd|pump client after iface config has changed

This corrects the ifdown script to detect if a dhcpcd client is running on an
interface regardless of its current config, allowing the client to be properly
killed after its BOOTPROTO has changed.

Comment 2 Bill Nottingham 2005-01-12 20:22:11 UTC

*** This bug has been marked as a duplicate of 127726 ***

Comment 3 Red Hat Bugzilla 2006-02-21 19:06:24 UTC
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.