Patch to prevent multiple dhclients starting on an interface

[David W. Hankins]

On Wed, Jun 15, 2005 at 01:36:01PM -0400, mcr wrote:
> >>>>> "David" == David W Hankins <David_Hankins at isc.org> writes:
>     David> Is this "please refresh my address?"  (In which case, it
>     David> would be far easier to either stop/start dhclient or prod the
>     David> existing daemon in some manner to elicit that result - there
>     David> exist already 'hibernate' and 'awaken' control states that do
>     David> this, which can be acheived through omapi today, or otherwise
>     David> would be a trivial excercise in coding to add signal handlers
>     David> to set these states...).
> 
>   Can you point to an example?

Do you mean an OMAPI how-to?  I'm not aware of one.

Best I can suppose is dhcp-client or dhcp-server mailing list archives.

>   I think that omapi still can't "add an interface", right?

That would mean 'ifup' in my mind not the 'please refresh my address'
translation I'm supposing.  For 'ifup' you do really want a new daemon.
For the 'please refresh' supposition of 'ifup --force', you do really
want to just poke the running daemon.

And no, omapi can't add an interface.


I'm not saying that the client as it stands fills the needs.  I'm
saying I don't understand the need, and threw out two guesses.

-- 
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