[Dnsmasq-discuss] Where does the complete dump go?

[richardvoigt at gmail.com]

On Fri, Jul 25, 2008 at 8:05 AM, Carlos Carvalho <carlos at fisica.ufpr.br>wrote:

> richardvoigt at gmail.com (richardvoigt at gmail.com) wrote on 25 July 2008
> 03:11:
>  >Evidently, it is turning logging *on* that presents the problem, because
> you
>  >can get no information about the state of the cache before dnsmasq was
>  >reloaded to enable logging.
>
> He should leave logging on all the time then, it's cheap enough.
>
> I'm against a signal for logging only. What would be interesting is a
> signal for reloading the config. It'd reload only what is possible of
> course but it can be done for most settings.


I think a better solution would be to split the functionality of the
log-queries option:

*-q, --log-queries* Log the results of DNS queries handled by dnsmasq.
Enable a full cache dump on receipt of SIGUSR1.
Clearly this controls two separate functions.  It would be good to have a
flag to enable full cache dump on SIGUSR1 without also logging every query.
For that matter, a numeric option that causes the next N queries to be
logged in detail following each SIGUSR1.


>
>
> _______________________________________________
> Dnsmasq-discuss mailing list
> Dnsmasq-discuss at lists.thekelleys.org.uk
> http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.thekelleys.org.uk/pipermail/dnsmasq-discuss/attachments/20080725/18104399/attachment.htm