[Dnsmasq-discuss] How does DNSMASQ handle large concurrent configure file updating request requests

Yongkang You yongkang.you at gmail.com
Mon Feb 9 07:33:15 GMT 2015


On Sun, Feb 8, 2015 at 6:35 AM, Simon Kelley <simon at thekelleys.org.uk>
wrote:

> Are you using the new config keywords
>
> dhcp-hostsdir
> dhcp-optsdir
>
hostsdir
>
> These are equivalent to dhcp-hostfile, dhcp-optsfile and addn-hosts
> when provided with a directory, except that they use inotify and don't
> need SIGUSR1.
>
> It's a bit of a pain to have yet more options, but the semantics are
> different than the existing ones, and we need to be able to error if
> someone asks for the new inotify behaviour when support isn't compiled
> in, or we're on a platform that doesn't support it.
>

okay. After I switched to dhcp-hostsdir and dhcp-optsdir, the magic
inotifies are coming!
I can see related logs in dnsmasq.log and VM does receive IP address
successfully.

But hostsdir doesn't work.  When new config file created, there isn't log
tracked in dsmasq.log and VMs can not use hostname to ping each other. Even
if I restart dnsmasq process, the config also work. The same config file
works when using addn-hosts option, when reboot dnsmasq process.




-- 
Yongkang You
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.thekelleys.org.uk/pipermail/dnsmasq-discuss/attachments/20150209/3fafbc04/attachment.html>


More information about the Dnsmasq-discuss mailing list