Editing dhcpd.conf without corrupting leases

A.L.M.Buxey at lboro.ac.uk A.L.M.Buxey at lboro.ac.uk
Tue Apr 14 08:18:21 UTC 2009


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!), then diff the new
file versus the old file - and if its changed, move it
across (after backing up the old version) and restart
the DHCPD process.

alternatively, migrate to a total DB solution and remove
the whole flat-file thing.


More information about the dhcp-users mailing list