Your message dated Thu, 7 Aug 2008 09:05:54 +1000
with message-id <[EMAIL PROTECTED]>
and subject line Re: Bug#493939: Wish for /etc/init.d/dnsmasq reload (kill -HUP)
has caused the Debian Bug report #493939,
regarding Wish for /etc/init.d/dnsmasq reload (kill -HUP)
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [EMAIL PROTECTED]
immediately.)
--
493939: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=493939
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: dnsmasq
Version: 2.45-1
Severity: wishlist
It would be nice if "/etc/init.d/dnsmasq reload" sent a HUP to
dnsmasq. From the manpage:
NOTES
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.
-- System Information:
Debian Release: lenny/sid
APT prefers testing
APT policy: (990, 'testing')
Architecture: i386 (i686)
Kernel: Linux 2.6.25-2-686 (SMP w/1 CPU core)
Locale: LANG=en_AU.utf8, LC_CTYPE=en_AU.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
--- End Message ---
--- Begin Message ---
On Wed, Aug 06, 2008 at 09:07:26PM +0100, Simon Kelley wrote:
>> It would be nice if "/etc/init.d/dnsmasq reload" sent a HUP to
>> dnsmasq.
>
> At one time this was exactly the behaviour, but it was removed as a
> policy violation because SIGHUP doesn't re-read [dnsmasq.conf].
> Unless policy has changed, I don't think it should be changed now.
Fair enough; closing this bug.
--- End Message ---
