Re: [Dnsmasq-discuss] rereading configuration files

2012-10-29 Thread Ed W
On 24/10/2012 18:59, Dan Williams wrote: On Tue, 2012-10-23 at 20:42 +0100, Simon Kelley wrote: On 23/10/12 20:21, Gene Czarcinski wrote: It would be useful to libvirt if dnsmasq would reread the configuration file and/or the files in the configuration directory upon demand (via SIG) as is done

Re: [Dnsmasq-discuss] rereading configuration files

2012-10-26 Thread Simon Kelley
On 26/10/12 15:02, Simon Kelley wrote: > On 24/10/12 18:59, Dan Williams wrote: > > This is a good example of the pitfalls: it possible to specify the local > address and port used to contact a server, thus: > > server=192.168.0.1@192.168.100.1#800 > > which ensures that queries sent to 192.168

Re: [Dnsmasq-discuss] rereading configuration files

2012-10-26 Thread Simon Kelley
On 24/10/12 18:59, Dan Williams wrote: > > One problem we ran into with NM, and why I posted the patch for the new > D-Bus interface call, was that updated DNS configuration is *not* > re-read on HUP. That means that whenever we change nameservers as a > result of DHCP renewal, connection of a V

Re: [Dnsmasq-discuss] rereading configuration files

2012-10-24 Thread Dan Williams
On Tue, 2012-10-23 at 20:42 +0100, Simon Kelley wrote: > On 23/10/12 20:21, Gene Czarcinski wrote: > > It would be useful to libvirt if dnsmasq would reread the configuration > > file and/or the files in the configuration directory upon demand (via > > SIG) as is done for some other files. > > > >

Re: [Dnsmasq-discuss] rereading configuration files

2012-10-23 Thread Simon Kelley
On 23/10/12 20:21, Gene Czarcinski wrote: It would be useful to libvirt if dnsmasq would reread the configuration file and/or the files in the configuration directory upon demand (via SIG) as is done for some other files. Right now, when minor changes are made to a network configuration, it is n