Greetings,
agreed.
On Mon, Jun 22, 2015 at 4:17 AM, reiner otto
wrote:
> For me, it would be a great advantage, to have the option to log requests
> and reponses only, both DHCP and DNS, but omitting intermediate steps. This
> might be made more flexible, like defining sections of code to be lo
Filtering the log should be a feature of your syslog daemon.
For example, this question on SuperUser explains how to exclude certain
message patterns:
http://unix.stackexchange.com/questions/52860/how-to-exclude-given-lines-in-syslog-ng
On Mon, Jun 22, 2015 at 12:23 AM, Albert ARIBAUD
wrote:
>
Hi,
with dbus interface enabled, the config dnsmasq runs with is something like
dynamic.
is there a way to see its current dns config at some time during its
execution?
___
Dnsmasq-discuss mailing list
Dnsmasq-discuss@lists.thekelleys.org.uk
http://list
For me, it would be a great advantage, to have the option to log requests and
reponses only, both DHCP and DNS, but omitting intermediate steps. This might
be made more flexible, like defining sections of code to be logged only, as in
squid. Or setting up classes of logs, like"debug" (as it is l
Hi all, maybe the OP should clarify what he wants to do. Just to unclutter
a log for debugging, the standard tools are fine (grep&c.).
Or does he parse the logs for another goal? Then, a terser format might
make sense - or a completely different approach.
Best,
Hartmut
Hi Richard,
The questio
