<html><body><div style="color:#000; background-color:#fff; font-family:Courier New, courier, monaco, monospace, sans-serif;font-size:13px"><div dir="ltr" id="yui_3_16_0_1_1435049912600_3393"><span id="yui_3_16_0_1_1435049912600_3421">Of course, this is an option. But, in case dnsmasq is used on embedded systems, which not even use syslog-ng for logging, the scenary changes. It does not make sense here, to either generate a lot of redundant traffic and CPU-load, OR to especially setup syslog-ng (if possible, because of limited flash mem), which also puts redundant load on the small CPU. </span></div> <br><div class="qtdSeparateBR"><br><br></div><div style="display: block;" class="yahoo_quoted"> <div style="font-family: Courier New, courier, monaco, monospace, sans-serif; font-size: 13px;"> <div style="font-family: HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif; font-size: 16px;"> <div dir="ltr"> <font face="Arial" size="2"> Richard Nelson <unixabg@gmail.com> schrieb am 2:32 Dienstag, 23.Juni 2015:<br> </font> </div> <br><br> <div class="y_msg_container"><div id="yiv1260824812"><div><div dir="ltr"><div>Greetings,<br clear="none"><br clear="none"></div>agreed.<br clear="none"><div><div><div class="yiv1260824812gmail_extra"><br clear="none"><div class="yiv1260824812gmail_quote">On Mon, Jun 22, 2015 at 4:17 AM, reiner otto <span dir="ltr"><<a rel="nofollow" shape="rect" ymailto="mailto:augustus_meyer@yahoo.de" target="_blank" href="mailto:augustus_meyer@yahoo.de">augustus_meyer@yahoo.de</a>></span> wrote:<br clear="none"><blockquote class="yiv1260824812gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><div class="yiv1260824812yqt8022119156" id="yiv1260824812yqt43584"><div><div style="color:#000;background-color:#fff;font-family:Courier New, courier, monaco, monospace, sans-serif;font-size:13px;"><div>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</div><div dir="ltr">"debug" (as it is like "log-queries" right now) and a more quiet, new "log-queries" only logging queries and responses.<br clear="none"></div><div><div class="yiv1260824812h5"><div><span></span></div> <br clear="none"><div><br clear="none"><br clear="none"></div><div style="display:block;"> <div style="font-family:Courier New, courier, monaco, monospace, sans-serif;font-size:13px;"> <div style="font-family:HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif;font-size:16px;"> <div dir="ltr"> <font face="Arial" size="2"> Hartmut Krafft <<a rel="nofollow" shape="rect" ymailto="mailto:hartmut@mail.ru" target="_blank" href="mailto:hartmut@mail.ru">hartmut@mail.ru</a>> schrieb am 9:43 Montag, 22.Juni 2015:<br clear="none"> </font> </div> <br clear="none"><br clear="none"> <div>Hi all, maybe the OP should clarify what he wants to do. Just to unclutter <br clear="none">a log for debugging, the standard tools are fine (grep&c.).<br clear="none">Or does he parse the logs for another goal? Then, a terser format might <br clear="none">make sense - or a completely different approach.<br clear="none">Best,<br clear="none">Hartmut<br clear="none"><br clear="none"><br clear="none">Hi Richard,<br clear="none"><br clear="none">The question is about controlling what is logged, not where it is (and<br clear="none">no, I don't have any idea except poor man's solutions such as filtering<br clear="none">the whole log -- wherever it comes from -- through grep plus tailf).<br clear="none"><br clear="none">Ammicalement,<br clear="none">Albert.<br clear="none"><br clear="none">Le Sun, 21 Jun 2015 20:23:27 -0500, "<a rel="nofollow" shape="rect" ymailto="mailto:richardvoigt@gmail.com" target="_blank" href="mailto:richardvoigt@gmail.com">richardvoigt@gmail.com</a>"<br clear="none"><<a rel="nofollow" shape="rect" ymailto="mailto:richardvoigt@gmail.com" target="_blank" href="mailto:richardvoigt@gmail.com">richardvoigt@gmail.com</a>> a écrit :<br clear="none"><br clear="none">> Configure dnsmasq to log via syslog, and filter there.<br clear="none">><br clear="none">> The relevant configuration option is:<br clear="none">><br clear="none">> *-8, --log-facility=<facility>* Set the facility to which dnsmasq will send<br clear="none">> syslog entries, this defaults to DAEMON, and to LOCAL0 when debug mode is<br clear="none">> in operation. If the facility given contains at least one '/' character, it<br clear="none">> is taken to be a filename, and dnsmasq logs to the given file, instead of<br clear="none">> syslog. If the facility is '-' then dnsmasq logs to stderr. (Errors whilst<br clear="none">> reading configuration will still go to syslog, but all output from a<br clear="none">> successful startup, and all output whilst running, will go exclusively to<br clear="none">> the file.) When logging to a file, dnsmasq will close and reopen the file<br clear="none">> when it receives SIGUSR2. This allows the log file to be rotated without<br clear="none">> stopping dnsmasq.<br clear="none">><br clear="none">> On Sun, Jun 21, 2015 at 7:48 PM, Richard Nelson <<a rel="nofollow" shape="rect" ymailto="mailto:unixabg@gmail.com" target="_blank" href="mailto:unixabg@gmail.com">unixabg@gmail.com</a>> wrote:<br clear="none">><br clear="none">> > Greetings,<br clear="none">> ><br clear="none">> ><br clear="none">> > On Sun, Jun 21, 2015 at 1:32 AM, reiner otto <<a rel="nofollow" shape="rect" ymailto="mailto:augustus_meyer@yahoo.de" target="_blank" href="mailto:augustus_meyer@yahoo.de">augustus_meyer@yahoo.de</a>><br clear="none">> > wrote:<br clear="none">> ><br clear="none">> >> Option "log-queries" generates a lot of info. Is there any means, to log<br clear="none">> >> less info ? Particularly, I am only interested in the DNS-request, arriving<br clear="none">> >> at dnsmasq.<br clear="none">> >><br clear="none">> >><br clear="none">> > I too am interested in how to achieve this.<br clear="none"><br clear="none">_______________________________________________<br clear="none">Dnsmasq-discuss mailing list<br clear="none"><a rel="nofollow" shape="rect" ymailto="mailto:Dnsmasq-discuss@lists.thekelleys.org.uk" target="_blank" href="mailto:Dnsmasq-discuss@lists.thekelleys.org.uk">Dnsmasq-discuss@lists.thekelleys.org.uk</a><br clear="none"><a rel="nofollow" shape="rect" target="_blank" href="http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss">http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss</a><div><br clear="none"><br clear="none"><br clear="none"><br clear="none">_______________________________________________<br clear="none">Dnsmasq-discuss mailing list<br clear="none"><a rel="nofollow" shape="rect" ymailto="mailto:Dnsmasq-discuss@lists.thekelleys.org.uk" target="_blank" href="mailto:Dnsmasq-discuss@lists.thekelleys.org.uk">Dnsmasq-discuss@lists.thekelleys.org.uk</a><br clear="none"><a rel="nofollow" shape="rect" target="_blank" href="http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss">http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss</a><br clear="none"></div><br clear="none"><br clear="none"></div> </div> </div> </div></div></div></div></div></div><br clear="none">_______________________________________________<br clear="none">
Dnsmasq-discuss mailing list<br clear="none">
<a rel="nofollow" shape="rect" ymailto="mailto:Dnsmasq-discuss@lists.thekelleys.org.uk" target="_blank" href="mailto:Dnsmasq-discuss@lists.thekelleys.org.uk">Dnsmasq-discuss@lists.thekelleys.org.uk</a><br clear="none">
<a rel="nofollow" shape="rect" target="_blank" href="http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss">http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss</a><br clear="none">
<br clear="none"></blockquote></div><br clear="none"></div></div></div></div></div></div><br><br></div> </div> </div> </div></div></body></html>