From: Ted Lemon Date: Fri, 6 Jun 1997 01:56:32 +0000 (+0000) Subject: Add a note about why the server doesn't restart with SIGTERM X-Git-Tag: DHCP-970605^2~1 X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=4e19a6dfc2e5fc391805528a3980193965b1450d;p=thirdparty%2Fdhcp.git Add a note about why the server doesn't restart with SIGTERM --- diff --git a/server/dhcpd.8 b/server/dhcpd.8 index e7a06ac83..b19fe34ca 100644 --- a/server/dhcpd.8 +++ b/server/dhcpd.8 @@ -132,6 +132,14 @@ process ID contained in and then re-invoke dhcpd. Because the DHCP server database is not as lightweight as a BOOTP database, dhcpd does not automatically restart itself when it sees a change to the dhcpd.conf file. +.PP +Note: We get a lot of complaints about this. We realize that it would +be nice if one could send a SIGHUP to the server and have it reload +the database. This is not technically impossible, but it would +require a great deal of work, our resources are extremely limited, and +they can be better spent elsewhere. So please don't complain about +this on the mailing list unless you're prepared to fund a project to +implement this feature, or prepared to do it yourself. .SH COMMAND LINE .PP The names of the network interfaces on which dhcpd should listen for