Anselm Lingnau wrote: > Subject: Allow "/etc/init.d/dnsmasq reload" > > Package: dnsmasq > > Version: 2.55-2 > > Severity: wishlist > Tags: patch > > According to the man page, dnsmasq listens to SIGHUP and will reload its > configuration files when the signal is received. It is common to enable the > "reload" action in init scripts to send SIGHUP to a daemon; however, the > Debian init script for dnsmasq does not appear to offer this. >
>From 'man dnsmasq': When it receives a SIGHUP, dnsmasq clears its cache and then re-loads /etc/hosts and /etc/ethers and any file given by --dhcp-hostsfile, --dhcp-optsfile or --addn-hosts. The dhcp lease change script is called for all existing DHCP leases. If --no-poll is set SIGHUP also re-reads /etc/resolv.conf. SIGHUP does NOT re-read the configuration file. ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Whilst it might be useful to have "reload" operation which does reload /etc/hosts, /etc/ethers etc it's not possible to do that without violating the Debian-policy, which says: "reload cause the configuration of the service to be reloaded without actually stopping and restarting the service." It also causes confusion: people expect that that /etc/init.d/dnsmasq reload will reload the configuration, and it doesn't. This functionality was present in long-ago versions of the dnsmasq package and was removed after bugs which were the precise mirror-image of this one were filed. Cheers, Simon. -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
