dhclient does not reliably exit when the device disappears

[David W. Hankins]

I consider this an architectural problem.  It's not proper for a daemon
that might listen to multiple interfaces to exit prematurely.
Particularly when the intended design of the product was to run at all
times, and suspend/resume when interfaces are removed and inserted in
the system.

As I said on the dhcp-client mailing list recently, architecturally we
want to move to a single-daemon-per-interface model, and from there it
makes a whole lot more sense to exit jsut as a sanity check if the
interface the daemon was targetted to goes away.

I'm not sure this will make it into 3.1, but it is on our list.

-- 
David W. Hankins		"If you don't do it right the first time,
Software Engineer			you'll just have to do it again."
Internet Systems Consortium, Inc.		-- Jack T. Hankins