>>>>> "MS" == Matthias Saou <[EMAIL PROTECTED]> writes:
MS> I wonder if that is possible... the init script for dhcpd does a
MS> "restart" when it is told to "reload", so I would imagine that it
MS> is not possible to have dhcpd use a new configuration without
MS> stopping/starting it.
I don't see how the manual page for dhcpd could be clearer:
Whenever changes are made to the dhcpd.conf file, dhcpd must be
restarted. To restart dhcpd, send a SIGTERM (signal 15) to the
process ID contained in /var/run/dhcpd.pid, 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.
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 techni� cally
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.
- J<
_______________________________________________
Seawolf-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/seawolf-list
