dhcpd 4.1.1

Steve Clark sclark at netwolves.com
Fri Jul 19 14:06:42 UTC 2013


On 07/19/2013 09:31 AM, Steven Carr wrote:
> Man page for DHCPD 4.1.1-P1 states:
>
> 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.
>
> ;)
>
>
Hi Steven,

Sorry for not reading the man page more carefully, I missed that part and went to end
where most man pages talk about using SIGHUP to cause the process to re-read its
conf file.

Anyway thanks for the pointer.

> On 19 July 2013 14:12, Steve Clark <sclark at netwolves.com <mailto:sclark at netwolves.com>> wrote:
>
>     On 07/19/2013 08:32 AM, Niall O'Reilly wrote:
>>     On 19 Jul 2013, at 13:27, Steve Clark wrote:
>>
>>>     Is there a way to make dhcpd re-read it conf file. I did
>>>     looked in the man page and did a quick google but didn't
>>>     see a way. Maybe via omapi?
>>     	Restarting dhcpd works for me.
>>
>>     	I suspect that the kind of method you suggest would
>>     	probably require stalling the service for a similar
>>     	duration as that caused by a restart.
>>
>>     	Niall O'Reilly
>>
>     I would really like something like send a SIGHUP, etc.
>
>

-- 
Stephen Clark
*NetWolves*
Director of Technology
Phone: 813-579-3200
Fax: 813-882-0209
Email: steve.clark at netwolves.com
http://www.netwolves.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.isc.org/pipermail/dhcp-users/attachments/20130719/ebb5d02a/attachment.html>


More information about the dhcp-users mailing list