Bug 137263

Summary: dhcpcd fails to stop
Product: [openSUSE] SUSE LINUX 10.0 Reporter: Jess Males <jmales>
Component: YaST2Assignee: E-mail List <bnc-team-screening>
Status: RESOLVED WONTFIX QA Contact: Klaus Kämpf <kkaempf>
Severity: Normal    
Priority: P5 - None    
Version: Final   
Target Milestone: ---   
Hardware: PC   
OS: Other   
Whiteboard:
Found By: Other Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---

Description Jess Males 2005-12-06 21:22:28 UTC 
Upon initial installation of OpenSUSE 10, I choose dhcp for configuring the network card.  Several days later, I configured a static IP address through the Yast2 interface, saved the changes and did nothing else.  As the changes took effect immediately, I didn't think to restart the network service or to restart the PC.

Evidently, the dhcp client (dhcpcd) was never killed.  It remained alive, and at the end of its lease, it overwrote my settings.  restarting the network component fixes this problem.

Yast2 needs to either kill the dhcpcd process or restart the network service.
Comment 1 Michael Gross 2005-12-07 13:32:47 UTC 
Please attach the yast logfiles of this scenario.
Comment 2 Michael Gross 2005-12-14 12:39:43 UTC 
Please reopen this bug if the information asked for (yast logfiles) can be provided. Thanks.
Comment 3 Stephan Kulow 2008-06-25 09:34:18 UTC 
mass reopening all SuSE Linux bugs that are set to REMIND+LATER to change the resolution to WONTFIX (adapting to new policy)
Comment 4 Stephan Kulow 2008-06-25 09:36:19 UTC 
mass reopening all SuSE Linux bugs that are set to REMIND+LATER to change the resolution to WONTFIX (adapting to new policy)
Comment 5 Stephan Kulow 2008-06-25 09:41:42 UTC 
mass reopening all SuSE Linux bugs that are set to REMIND+LATER to change the resolution to WONTFIX (adapting to new policy)
Comment 6 Stephan Kulow 2008-06-25 09:53:09 UTC 
Closing old LATER+REMIND bugs as WONTFIX - if you still plan to work on it, feel free to reopen and set to ASSIGNED.

In case the report saw repeated reopen comments, it's due to bugzilla timing out on the huge request ;(