Editing dhcpd.conf without corrupting leases

[Darren]

Perhaps they have some problem with their init scripts - sending  
signal 9 instead of 15 or similar that doesn't allow dhcpd to finish  
its current task before exiting (Although, I think David Hankins said  
there is no special signal handling anyway).  A second possibility  
could be that they have enormous amounts of activity from a large  
customer base or very short lease times, so that dhcpd is almost  
constantly writing to the lease file.

On Apr 14, 2009, at 8:03 AM, John Hascall wrote:

>
>> when you get to this sort of large numbers of static hosts
>> and modification numbers then the best way is to move all
>> of it to a DB back end. generate a dhcpd.conf.new from
>> the DB entries, then do a sanity check (hopefully the
>> code producing the config file from the DB will stop
>> weird and broken entries anyway!)
>
> While I agree with this, I'm not sure it solves the OP's
> problem which is a corrupt leases file, not a corrupt
> config file.
>
> I'm still wondering how the OP is (multiple times) seeing a
> corrupt leases file on restart, because I just checked my logs
> and we've done over a million dhcp restarts since we started
> with 'NetReg' and have yet to see this.  Either there must be
> some fundamental difference in our installations or they are
> doing jillions of restarts and/or are the unluckiest bastards
> on the planet.
>
> John
> _______________________________________________
> dhcp-users mailing list
> dhcp-users at lists.isc.org
> https://lists.isc.org/mailman/listinfo/dhcp-users
>