It is nice that the initscript will create your lease file for you; I used to muck around with the initscripts to do this myself. However, this system creates false failures if the lease file is move. For instance, if /etc/dhcp/dhcpd.conf contains lease-file-name "/tmp/dhcpd.lease"; pid-file-name "/tmp/dhcpd.pid"; (necessarily in the global scope), AND there is no /var/lib/dhcp directory, then the initscript will fail even though nothing is actually wrong. I don't have a good, simple idea for fixing this. I suppose you could parse the dhcpd.conf file in the initscript, but that seems unusual. You could add an option in the conf.d/dhcp file, but the user would have to keep their conf.d/dhcp and dhcpd.conf synchronized. The best idea I can think of is to use the conf.d/dhcp approach, but with the dhcpd -lf option. That way the dhcpd.conf file can remain ignorant of the lease configuration, and gentoo can happily verify lease file existence. -Paul Komarek
I just noticed that the dhcpd.pid file works the same way as the lease file. If the lease file becomes changeable, then probably the pid file should, too. BTW, this sort of thing comes up with embedded systems. I'm not sure how broad the appeal of this type of feature is.
Mass reassign wrt Bug 23718, maintainer being retired.
Fixed in dhcp-3.0.3-r1
