<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On Wed, Jan 29, 2014 at 9:44 AM, Sebastian Moeller <span dir="ltr"><<a href="mailto:moeller0@gmx.de" target="_blank">moeller0@gmx.de</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div class="im">On January 29, 2014 5:10:18 PM CET, Dave Taht <<a href="mailto:dave.taht@gmail.com">dave.taht@gmail.com</a>> wrote:<br>
>On Wed, Jan 29, 2014 at 4:45 AM, Sebastian Moeller <<a href="mailto:moeller0@gmx.de">moeller0@gmx.de</a>><br>
>wrote:<br>
>> Hi Dave,<br>
>><br>
>> quick question, how does one turn of logging for babeld? It seems<br>
>that if daemonized it defaults to logging to /var/log/babeld.log (or<br>
>similar). Is setting the log file to /dev/null really the answer?<br>
><br>
>seems so.<br>
<br>
</div> Okay, I guess I will try that then...<br></blockquote><div><br></div><div>Here's the directive I'm using in /etc/babeld.conf</div><div><br></div><div>log-file /dev/null<br></div><div><br></div><div>and then you can restart either via the web gui or `/etc/rc.d/S70babeld restart`</div>
<div><br></div></div></div></div>