will dynamic dhcpd.conf be supported in future releases
mitch at ccmr.cornell.edu
Fri Aug 11 17:37:46 UTC 2006
On Fri, 11 Aug 2006, David W. Hankins wrote:
> For a small number of people who have very large problems, it is
> intriguing to consider that we might make dhcpd process a HUP to:
> 1) Fork and execv dhcpd - continue like nothing's changed.
> 2) Receive a SIGCHLD when the new dhcpd fork()s (which it
> will do after reading dhcpd.conf and dhcpd.leases).
> 3) Exit.
> There is one major complication in such a mechanism. The child
> daemon MUST have a way to obtain any changes in state between the
> fork and the exit.
Major? Think of it like a journaled filesystem. Just before the
fork, start a journal file. When the parent process exits, the
child reads and processes the journal. I must be missing something
More information about the dhcp-users