Thomas Hood wrote:
Package: dnsmasq
Version: 2.20-1
Severity: normal

I just started using dnsmasq again after a couple of months and I find
that the current version of dnsmasq does not re-read resolv.conf when
it is updated.  Sending SIGHUP to the process causes it to re-read
/etc/hosts but not resolv.conf.

$ ps -lf -C dnsmasq
F S UID        PID  PPID  C PRI  NI ADDR SZ WCHAN  STIME TTY TIME CMD
5 S nobody    2773     1  0  76   0 -   437 -      08:55 ?  00:00:00 
/usr/sbin/dnsmasq -r /var/run/dnsmasq/resolv.conf


-- System Information: Debian Release: 3.1 APT prefers testing APT policy: (500, 'testing'), (50, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.10 Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15)

Versions of packages dnsmasq depends on:
ii  libc6                       2.3.2.ds1-20 GNU C Library: Shared libraries an
ii  netbase                     4.20         Basic TCP/IP networking system

-- no debconf information



Just to get things straight: by default dnsmasq checks the mtime of resolv.conf and re-reads it when the mtime changes. In this mode it does _not_ re-read resolv.conf on a SIGHUP.


Setting the --no-poll flag or adding it to /etc/dnsmasq.conf changes the behaviour to more traditional re-read the file on SIGHUP mode.

I'm not clear which mode is in use here, but both seem to be working fine for me, so a more detailed check on the reason for the problem is going to be needed.

Cheers,

Simon.


-- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Reply via email to