[CentOS] Lingering dhclient issue
jrandall at comwave.net
Thu Sep 14 00:41:53 UTC 2006
>Yes, it would. My question was what is the recommended process to
>switch an interface from DHCP to STATIC so that the dhclient process
>automatically gets killed. Doing an "ifdown eth0", editing the
>configuration file, and then doing an "ifup eth0" left this lingering
>dhclient process around.
If you're looking for a one command solution after making the required configuration changes, using the "service network restart" is likely your best bet. If you don't want to restart the entire network (which can cause service interuption depending on what is being serviced over the network), simply carrying out the steps you originally outlined while killing the dhclient process acting on the interface is probably the best approach since there is no association between ifconfig and dhclient.
From: Alfred von Campe [mailto:alfred at 110.net]
Sent: Wed 9/13/2006 7:27 PM
To: CentOS mailing list
Subject: Re: [CentOS] Lingering dhclient issue
On Sep 13, 2006, at 17:07, Johnny Hughes wrote:
> I do:
> service network restart
I'll remember this for next time. If I get a chance, I will also
test this to see if the dhclient process indeed goes away.
On Sep 13, 2006, at 18:29, Justin Randall wrote:
> Unless this device is going to be switching from DCHP to static
> frequently, wouldn't simply killing the dhclient process be
Yes, it would. My question was what is the recommended process to
switch an interface from DHCP to STATIC so that the dhclient process
automatically gets killed. Doing an "ifdown eth0", editing the
configuration file, and then doing an "ifup eth0" left this lingering
dhclient process around.
CentOS mailing list
CentOS at centos.org
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 3174 bytes
Desc: not available
Url : http://lists.centos.org/pipermail/centos/attachments/20060913/dd71be25/attachment.bin
More information about the CentOS