From: Sebastian Moeller <moeller0@gmx.de>
To: Steve Jenson <stevej@fruitless.org>
Cc: "cerowrt-devel@lists.bufferbloat.net"
<cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] cerowrt issues (3.10.24-8)
Date: Wed, 29 Jan 2014 20:55:40 +0100 [thread overview]
Message-ID: <1CB745C6-5334-4CF8-8535-BB97E9B37A1D@gmx.de> (raw)
In-Reply-To: <CABiHZ_U9SceKfUS5-2kCiKYfEfWGHoOkEXbLKJaFfNfxPureDw@mail.gmail.com>
Hi Steve,
On Jan 29, 2014, at 19:24 , Steve Jenson <stevej@fruitless.org> wrote:
> On Wed, Jan 29, 2014 at 9:44 AM, Sebastian Moeller <moeller0@gmx.de> wrote:
> On January 29, 2014 5:10:18 PM CET, Dave Taht <dave.taht@gmail.com> wrote:
> >On Wed, Jan 29, 2014 at 4:45 AM, Sebastian Moeller <moeller0@gmx.de>
> >wrote:
> >> Hi Dave,
> >>
> >> quick question, how does one turn of logging for babeld? It seems
> >that if daemonized it defaults to logging to /var/log/babeld.log (or
> >similar). Is setting the log file to /dev/null really the answer?
> >
> >seems so.
>
> Okay, I guess I will try that then...
>
> Here's the directive I'm using in /etc/babeld.conf
>
> log-file /dev/null
>
> and then you can restart either via the web gui or `/etc/rc.d/S70babeld restart`
Ah, thanks. Since I am on 3.10.28-1 this was /etc/init.d/babeld restart. And I opted for putting:
option 'log-file' '/dev/null'
into /etc/config/babeld, since that seemed the more openwork way of doing things; I wonder whether it really is wise to carry both files…
Babeld runs again, and no /var/log/babeld.log appeared, but whether it works I do not know (and I doubt it given that babeld.log was growing due to nasty repeating error messages...)
Best Regards
Sebastian
>
next prev parent reply other threads:[~2014-01-29 19:55 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-24 23:08 Steve Jenson
2014-01-24 23:23 ` Dave Taht
2014-01-27 21:06 ` Steve Jenson
2014-01-27 21:10 ` Steve Jenson
2014-01-27 21:14 ` Dave Taht
2014-01-29 12:45 ` Sebastian Moeller
2014-01-29 16:10 ` Dave Taht
2014-01-29 17:44 ` Sebastian Moeller
2014-01-29 18:21 ` Dave Taht
2014-01-29 19:51 ` Sebastian Moeller
2014-01-29 19:56 ` David Personette
2014-01-29 20:04 ` Sebastian Moeller
2014-01-29 18:24 ` Steve Jenson
2014-01-29 19:55 ` Sebastian Moeller [this message]
2014-01-30 16:21 ` Dave Taht
2014-01-30 18:46 ` Sebastian Moeller
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://lists.bufferbloat.net/postorius/lists/cerowrt-devel.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1CB745C6-5334-4CF8-8535-BB97E9B37A1D@gmx.de \
--to=moeller0@gmx.de \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=stevej@fruitless.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox