IIRC isc-dhcpd is unlike any other daemon I know of, in that if you send it SIGHUP it will not reload the configuration/handles, it will just die. That said, this is behavior is intentional according the developers, so the best way to reload it is simply service isc-dhcpd restart. There should be a way to perform this from within newsyslog(8), but I don't recall how off the top of my head.
As far as I know you don't need to 'kick' the dhcpd because it logs through syslog itself. So it's not dhcpd that has the file opened, it's syslogd(8).
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.