Multiple DHCP server processes

[Jim Hribnak]

This is exactly what we do..  we queue up additions to the dhcp.conf file
and then make the changes on the 5 minute mark if there is anything queued
up.  It has worked flawlessly  for the last 7 years or so.  If something
needs to be tweaker (which is rare) and in most causes someone put the
person in the wrong group, and that has to be changed at which point it is a
manual change and a manual restart.,


Jim

-----Original Message-----
From: dhcp-users-bounce at isc.org [mailto:dhcp-users-bounce at isc.org] On Behalf
Of markd
Sent: Thursday, May 25, 2006 10:59 AM
To: dhcp-users at isc.org
Subject: Re: Multiple DHCP server processes



> we have considered also such solution, but unfortunately it is not
acceptable 
> - we need that changes take effect immediately (often the scenario is the 
> following - the person who makes onsite customer installations or 
> troubleshootings  calls our operator and asks him to change some
parameters 
> for this customer which requires dhcpd restart and he can not wait for 
> scheduled intervals).

There are options in between "immediate" and every half hour.

We also have regular changes that require restart.  We queue them,
and a job runs every 5 minutes and only restarts if there's something
in the queue.  The field people have to wait on average a couple
minutes.  This keeps the thrashing way down, since in our setup
there are sometimes dozens of requests within a minute or two,
and other times, none for hours.

Mark