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

Mon Feb 9 15:49:30 GMT 2015

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On 09/02/15 07:33, Yongkang You wrote:
> 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.
> 
> 
> 
> 

You should see something like

dnsmasq: inotify, new or changed file /tmp/hosts/testone
dnsmasq: read /tmp/hosts/testone - 1 addresses

Just to check the argument to hostsdir is a directory, and not a file?

Any errors logged at startup?

Cheers,

Simon.