Added by Seth Mos almost 15 years ago. Updated over 13 years ago.
0%
Description
After disabling a opt2 interface on a dummy vlan, dhclient was still running and spamming the logs after I disabled the interface.
Updated by Chris Buechler over 14 years ago
No change, still leaves it running.
Updated by Seth Mos almost 14 years ago
I just tested this with a clean 2.0 BETA5 i386 install and I still see dhclient messages in the system logs.
Updated by Seth Mos almost 14 years ago
Hi, in the 2011 02 02 snapshot the dhclient still isn't killed when switching to static from the console or UI.
Feb 3 12:38:55 dhclient: FAIL
2.0-BETA5 (i386)
built on Wed Feb 2 23:56:12 EST 2011
Updated by Ermal Luçi almost 14 years ago
Found the remaining issue.
The previous, dhcp, interface type information was being lost when the apply changes button was clicked so no attempt to kill dhclient was made. Now dhclient will be killed and apply changes will put the new ip in place.
Updated by rancor rancor over 13 years ago
It seems to work now.
Before I disable vlan203 the dhclient is running
$ ps ax | grep dhclient
8629 ?? Is 0:00.00 dhclient: em0 [priv] (dhclient)
12493 ?? Ss 0:00.00 dhclient: em1_vlan203 [priv] (dhclient)
14048 ?? Is 0:00.10 dhclient: em0 (dhclient)
17124 ?? S 0:00.00 sh -c ps ax | grep dhclient
17737 ?? S 0:00.00 grep dhclient
50794 ?? Ss 0:00.00 dhclient: em1_vlan203 (dhclient)
And after I disable it
$ ps ax | grep dhclient
8629 ?? Is 0:00.00 dhclient: em0 [priv] (dhclient)
14048 ?? Ss 0:00.10 dhclient: em0 (dhclient)
29088 ?? S 0:00.00 sh -c ps ax | grep dhclient
29659 ?? S 0:00.00 grep dhclient
Case closed?
// rancor
Updated by Ermal Luçi over 13 years ago
Updated by