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

[Simon Kelley]

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

> 

> 
>> 
>> The simple way to implement this simply adds new configuration
>> from new files, if a file gets changed or deleted, then the
>> dhcp-hosts that were created by its old contents are not deleted,
>> and SIGUSR1 is still needed to re-read the config from scratch
>> and garbage collect old entries. More complex implementation
>> would keep track which dhcp-hosts are associated with which
>> files, and delete old versions when a file changes. I'd rather
>> not have to do the more complex version, is it can be avoided.
>> 
>> Comments?
>> 
>> 
> Thanks Simon! I will currently use some workaround and wait for the
> super inotify solution.
> 


There's some code in the git repo now, or download the 2.73test6 tarball.

I've added a new config option --dhcp-hostsdir, which reads all the
files in a directory in the same was as --dhcp-hostsfile, but doesn't
need SIGHUP to do it.

Let me know how you get on.



Cheers,

Simon.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQIcBAEBCAAGBQJUvsFWAAoJEBXN2mrhkTWiarQP/R9BuIv+zWv2mCoMww26xq+x
ztM/EzGPVpkoceBQTRaur4rrKfCHBfRKBgwudKLGQ33ZcPhKFVHl6dQa6Jfrk7FT
D2z/AEdq9t+ifjBUM8BZzYK95pfDpABBng6TdpyY7mJlHhoybrLdOSjq72ZhM9IO
wFKCt9eQV8rdZPoqm9rJxKtWj6BmuC9LY/YMUeWhDcrc6fuGRCpOg+PLcqOWmJit
dDBvSJ/TEu7+pPz7J5y8BQJejXOeNzzNvyrLN/KgU9407LA6EZHBsQnPJyN0C2Zq
Yyio7d4bXAQCvT4RNUYOfTjk9pNRI8BKAQPAEVmWMhskxdMYcXIcd3+NGFnW+V6q
XFfCCbLH+dV/V+MjkiC57n51bXvFXDOCKW5JfUcpX1avs24hP7zSw5LNUmwCJrbe
qZBdFjKbpoLPbugnqYmIaQhjWMVsLU5fttvFtIQJBHLSNQR0UGggfhLsw9+ANWi3
kfgnL/PZoMLFfWla95ITylMLQdJd0DdPm0nS8hZDCzvjFHgM4WaPMp60vLkOy45t
Y/cA/rcLKhMtyMK1UY0ik51VoV/DQCxo9rf6rTU1EQPVsx514wHqeZ9FqLhNpWJS
RUNlUZ3mVfvkoknRsv6pWb9DfmFsGqxnfRG+NA36uhuNwnADt2FdNKtg14mBkMoS
FfVCiLVgd9ATszBp+P8D
=Bk0q
-----END PGP SIGNATURE-----