When dhcpd is first installed, there is no lease database. However,
dhcpd requires that a lease database be present before it will start.
To make the initial lease database, just create an empty file called
-DBDIR/dhcpd.leases.
+DBDIR/dhcpd.leases. You can do this with:
+.PP
+.nf
+ touch DBDIR/dhcpd.leases
+.fi
.PP
In order to prevent the lease database from growing without bound, the
file is rewritten from time to time. First, a temporary lease
database is created and all known leases are dumped to it. Then, the
old lease database is renamed DBDIR/dhcpd.leases~. Finally, the
newly written lease database is moved into place.
-.PP
-There is a window of vulnerability where if the dhcpd process is
-killed or the system crashes after the old lease database has been
-renamed but before the new one has been moved into place, there will
-be no DBDIR/dhcpd.leases. In this case, dhcpd will refuse to start,
-and will require manual intervention. \fBDO NOT\fR simply create a
-new lease file when this happens - if you do, you will lose all your
-old bindings, and chaos will ensue. Instead, rename
-DBDIR/dhcpd.leases~ to DBDIR/dhcpd.leases, restoring the old, valid
-lease file, and then start dhcpd. This guarantees that a valid lease
-file will be restored.
.SH FORMAT
Lease descriptions are stored in a format that is parsed by the same
recursive descent parser used to read the
.B dhcpd(8)
was written by Ted Lemon <mellon@vix.com>
under a contract with Vixie Labs. Funding
-for this project was provided by the Internet Software Corporation.
-Information about the Internet Software Consortium can be found at
-.B http://www.isc.org/isc.
+for this project was provided by the Internet Software Consortium.
+Information about the Internet Software Consortium can be found at:
+.B http://www.isc.org/