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

[Yongkang You]

On Wed, Feb 18, 2015 at 4:59 AM, Simon Kelley <simon at thekelleys.org.uk>
wrote:

>
> Changing the dnsmasq configuration, specifically dhcp-host entries,
> won't affect any current DHCP leases, so if you want to end a DHCP
> lease early (maybe to re-use the address) then you'll need to call use
> dhcp_release. That can be before or after sending SIGHUP it doesn't
> matter.
>

Simon,

Thanks for clear explanation. Then I think I might find a bug. I manually
execute dhcp_release. I can also see the log like:

 Feb 15 06:12:45 dnsmasq-dhcp[3521]: DHCPRELEASE(eth2) 10.11.0.3
fa:e1:51:0b:a5:00

But when I try to assign the IP to a new MAC, dnsmasq still report:

 Feb 15 06:13:13 dnsmasq[3521]: duplicate dhcp-host IP address 10.11.0.3 at
line 1 of /etc/hosts.dhcps//fa:e9:4a:40:7f:00

And when the VM is starting up, dnsmasq.log will say:

 Feb 15 06:13:23 dnsmasq-dhcp[3521]: DHCPDISCOVER(eth2) fa:e9:4a:40:7f:00
no address available

Do you think if it is an issue?

BTW, if dhcp_release works, I think it might be faster than inotify finds
the config is missed.

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