On Mon, 2005-03-21 at 08:47 +0000, Simon Kelley wrote:
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.
I am running in default mode, but dnsmasq is not re-reading the file.
I should mention that this happens after an APM suspend and resume. I just tried downing and upping and interface (without suspending and resuming) and this time dnsmasq did re-read the file after resolvconf updated it.
So it seems that dnsmasq is unhappy with something that happens on APM suspend and resume.
I suspect the problem is that _nothing_ happens at suspend/resume. Dnsmasq just checks the mtime of the file, and if that's more recent than the last time it checked the file, it re-reads it. Are you expecting something to happen over a suspend/resume cycle that would update the file? Does it occur? What happens to the mtime of the file?
One thing to bear in mind: dnsmasq doesn't spin checking the file all the time: it only polls it when it has work to do, so touching the file ins't enough to get it to re-read, you have to touch the file and then do a DNS query. The query will wake up dnsmasq, and it will then check resolv.conf and re-read it just before dealing with the query.
Cheers,
Simon.
-- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
