After suspend-and-resume I have problems with other applications such as squid and pan which access the network. In their case they use 100% CPU until they are restarted. dnsmasq, in contrast, does not use 100% CPU and it responds to signals; but it doesn't notice that resolv.conf has changed.
I am beginning to suspect that there is an obscure problem here involving the particular kernel version and the particular firmware I have.
Possibly, it is certainly the case that nothing in dnsmasq that deals with re-reading resolv.conf has changed for a long time, so if this used to work and doesn't now, probably something else changed.
Cheers,
Simon.
-- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
