Re: [Dnsmasq-discuss] Reading the dhcp.leases file

2017-02-14 Thread Reddeiah Raju Konduru
Sorry wrong Thread. On Tue, Feb 14, 2017 at 10:48 AM, Reddeiah Raju Konduru wrote: > Hi Simon, > > Thanks for the DHCP Client-ID's patch. > > - Raju > > > > On Tue, Feb 14, 2017 at 7:10 AM, Simon Kelley > wrote: > >> -BEGIN PGP SIGNED

Re: [Dnsmasq-discuss] Reading the dhcp.leases file

2017-02-14 Thread Reddeiah Raju Konduru
Hi Simon, Thanks for the DHCP Client-ID's patch. - Raju On Tue, Feb 14, 2017 at 7:10 AM, Simon Kelley wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA256 > > Albert's suggestions are good, and you can't reliably read the leases > file - in gets modified by

Re: [Dnsmasq-discuss] Reading the dhcp.leases file

2017-02-14 Thread Simon Kelley
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Albert's suggestions are good, and you can't reliably read the leases file - in gets modified by delete-and-rewrite, so if the timing is wrong, you'll see an incomplete write. DHCP script gets all the information needed to maintain a database

Re: [Dnsmasq-discuss] Reading the dhcp.leases file

2017-02-11 Thread Albert ARIBAUD
Hi Sam, Le Sat, 11 Feb 2017 16:06:55 -0600 Sam Weber a écrit: > In our system, when a change occurs to the DNS entries we want > dnsmasq to respond to, we scan the directory of active entries and > then grep the dhcp.leases file to see if the entry exists there. If > the

[Dnsmasq-discuss] Reading the dhcp.leases file

2017-02-11 Thread Sam Weber
In our system, when a change occurs to the DNS entries we want dnsmasq to respond to, we scan the directory of active entries and then grep the dhcp.leases file to see if the entry exists there. If the entry is not found in the leases file, we omit it. Once the scan and check is completed, we