Bug#240019: dhcp3-server: lease file remains empty, except for the boilerplate text

[David W. Hankins]

On Fri, Sep 16, 2005 at 03:54:23PM +1000, Andrew Pollock wrote:
> I've had a couple of users report that fixed address assignments don't
> get written to dhcpd.leases, but leases assigned out of the pool do.

Due to popular demand, the next feature release will support at least
"reserved" flagged dynamic leases if not bootp leases.

I initially thought that there exists already code on HEAD to do this,
but on later inspection it seems instead to be code that missed the
pullup from 3.0.1rc6 or thereabouts (the diff adds the FTS_BOOTP and
FTS_RESERVED states, which were removed in that release).

This planned feature will allow the admin to specify a dynamic range,
and config syntax will be provided to mark individual lease ownership
and its reserved status.

These get treated as normal leases - they go through the full gamut
of FREE/ACTIVE/EXPIRED, with the exception that the failover protocol
treats them differently - the primary and secondary will disagree about
their state intentionally, the primary will record them as FREE, the
secondary will record them as BACKUP.

Internally, each server will queue them on a 'reserved list' instead
of polluting either the 'free' or 'backup' lists (so allocate_lease()
does not have to learn to hunt down the lists beyond the first entry).

-- 
David W. Hankins		"If you don't do it right the first time,
Software Engineer			you'll just have to do it again."
Internet Systems Consortium, Inc.		-- Jack T. Hankins