status update: events working, first methods implemented; generally happy

Jörg Sommer joerg at alea.gnuu.de
Wed Jun 20 12:49:29 UTC 2007


Hallo martin,

martin f krafft <madduck at debian.org> wrote:
> For the sake of clarity, here is what happens if the user requests
> an interface to be brought up with DHCP:
>
>   4. the handler notifies the DHCP provider, which spawns a thread;
>      the event handler then simply waits on the event to complete;
>      the DHCP provider now has a write-only channel to the client
>      socket.
>
>   5. dhclient is invoked and issues the PREINIT event. This causes
>      the handler thread to queue a LINK event with parameters
>      "$IFACE up" and wait for the event to complete. dhclient will
>      wait for the completion of dhclient-script, which waits for the
>      handler thread, so we're more or less synchronous now.
>
>   5b. upon completion of the event, the handler may issue
>       a configuration event to erase all IPs from the interface and
>       add only 0.0.0.0; this is what dhclient-script does.
>
>   6. upon completion of the event, dhclient attempts to get a lease
>      and if it does, it releases an IFCFG event with the details.
>      All status information is written to the client socket.
>
>   7. the daemon dispatches this event to events.handlers.IFCFG,
>      which invokes methods/static.sh to do the actual work.
>
>   8. when the script returns, the daemon marks the IFCFG event
>      completed, which causes the dhclient handler thread to mark the
>      CTLSOCK_IFUP event as completed, which causes the control
>      socket thread to exit.

What happens with the DHCP provider? Does it alive? Who cares about
renewing the lease after lease time is over?

Ciao, Jörg.
-- 
“Programming today is a race between software engineers striving to
build bigger and better idiot—proof programs, and the Universe trying
to produce bigger and better idiots. So far, the Universe is winning.”
(Rich Cook)



More information about the netconf-devel mailing list