Project

General

Profile

Bug #259

When disabling a dhcp interface, dhclient is not stopped

Added by Seth Mos almost 10 years ago. Updated over 8 years ago.

Status:
Resolved
Priority:
Low
Assignee:
-
Category:
Interfaces
Target version:
Start date:
12/29/2009
Due date:
% Done:

0%

Estimated time:
Affected Version:
2.0
Affected Architecture:

Description

After disabling a opt2 interface on a dummy vlan, dhclient was still running and spamming the logs after I disabled the interface.

Associated revisions

Revision 5d478ecc (diff)
Added by Ermal Luçi over 9 years ago

Ticket #259. Search for the dhclient process using the real interface rather than the friendly one.

Revision 79d3a7cf (diff)
Added by Ermal Luçi over 9 years ago

Ticket #259. Retrun only the first pid from the list that might be found. This should fix not killed dhclient processes.

Revision bcfe4ae5 (diff)
Added by Ermal Luçi over 8 years ago

Ticket #259 trim the \n from the command output and return only the numeric part of it.

Revision 1f676b67 (diff)
Added by Ermal Luçi over 8 years ago

Ticket #259. Actually kill dhlient when the interface type changes before going through apply changes otherwise the information would be lost and dhclient will remain running.

History

#1 Updated by Ermal Luçi over 9 years ago

  • Status changed from New to Feedback

#2 Updated by Chris Buechler over 9 years ago

  • Status changed from Feedback to New

No change, still leaves it running.

#3 Updated by Ermal Luçi over 9 years ago

  • Status changed from New to Feedback

More fixes.

#4 Updated by Chris Buechler over 9 years ago

  • Status changed from Feedback to Resolved

fixed

#5 Updated by Seth Mos over 8 years ago

  • Status changed from Resolved to Feedback

I just tested this with a clean 2.0 BETA5 i386 install and I still see dhclient messages in the system logs.

#6 Updated by Jim Pingle over 8 years ago

  • Status changed from Feedback to New

#7 Updated by Ermal Luçi over 8 years ago

  • Status changed from New to Feedback

#8 Updated by Seth Mos over 8 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

#9 Updated by Ermal Luçi over 8 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.

#10 Updated by rancor rancor over 8 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

#11 Updated by Ermal Luçi over 8 years ago

  • Status changed from Feedback to Resolved

Also available in: Atom PDF