Dan Williams c34cc017ba dhcp: handle client early exit correctly ... When the client exits it may take a short amount of time for the dhclient hook script to deliver the options to NetworkManager; so we need to keep the client object around a bit (so we know what NMDHCPClient the options getting delivered are for). If we don't, the DHCPManager will dispose of the DHCPClient object and then when the options come in, it can't match up the PID from the options with the PID of an existing NMDHCPClient. So put the clients on a removal timer that keeps them around for a bit before we let the manager dispose of them. Since we're keeping the PID around too instead of zeroing it when the client exits (for the reason above), track whether the client is really dead yet so we don't indiscriminately kill a random process that happens to re-use the PID.		2010-05-02 00:24:40 -07:00
..
Makefile.am	dhcp: update logging	2010-04-06 18:07:18 -07:00
nm-dhcp-client.c	dhcp: handle client early exit correctly	2010-05-02 00:24:40 -07:00
nm-dhcp-client.h	dhcp: handle client early exit correctly	2010-05-02 00:24:40 -07:00
nm-dhcp-dhclient.c	dhcp: clean up client spawn return value	2010-05-01 09:53:49 -07:00
nm-dhcp-dhclient.h	dhcp: make client selection more forgiving	2010-03-23 14:22:10 -07:00
nm-dhcp-dhcpcd.c	dhcp: clean up client spawn return value	2010-05-01 09:53:49 -07:00
nm-dhcp-dhcpcd.h	dhcp: make client selection more forgiving	2010-03-23 14:22:10 -07:00
nm-dhcp-manager.c	dhcp: handle client early exit correctly	2010-05-02 00:24:40 -07:00
nm-dhcp-manager.h	dhcp: make client selection more forgiving	2010-03-23 14:22:10 -07:00