From: Alan Jenkins <alan.christopher.jenkins@gmail.com>
To: Sebastian Moeller <moeller0@gmx.de>
Cc: cerowrt-devel@lists.bufferbloat.net
Subject: Re: [Cerowrt-devel] [sqm-scripts] not started at boot?
Date: Tue, 3 Mar 2015 22:39:42 +0000 [thread overview]
Message-ID: <CANmMgnGc2pm7dRv4g_KRzg20vio9CZf1nykKy7qXFjhgi8Dm7Q@mail.gmail.com> (raw)
In-Reply-To: <37283C9D-E6A5-4C2A-9079-FCC9EACDED83@gmx.de>
On 03/03/2015, Sebastian Moeller <moeller0@gmx.de> wrote:
> Hi Alan,
> Excellent, now we have positive results from CC (you are running CC I
> believe) and cerowrt.
I'm afraid I'm running BB with this package manually installed.
>>
>> It still logs errors.
>
> In the boot log? I tend to consider these not as errors but as valid
> information; as long as sqm-scripts is still being tested I want it to be
> verbose, so I have an easier time actually helping people… But once we agree
> it is stable I will try to make it a bit more quiet…
The success messages make me happy too. By errors, I meant lines like
$ log.txt < grep 'Cannot find device "pppoe-wan"' | wc -l
22
presumably because /etc/init.d/sqm is still assuming pppoe-wan (or so)
exists, and dies noisily because ppp hasn't started yet.
>> Probably only from running the initscript first, it was just so noisy I
>> thought it was still happening for every interface that came up :). I
>> used `uci set system.@system[0].log_size=200; uci commit` to prevent log
>> overflow.
>
> Now that is useful, I always thought that this is a kernel default and can
> not be changed; so I learned something useful.
openwrt apparently uses busybox logd daemon (in userspace). I
discovered it doesn't use files by default and has a small buffer in
memory, accessed using the `logread` command.
Kernel log buffer (`dmesg` command) is separate. It can be sized
using the kernel boot option... log_buf_len.
https://www.kernel.org/doc/Documentation/kernel-parameters.txt
Alan
next prev parent reply other threads:[~2015-03-03 22:39 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-15 14:39 Alan Jenkins
2015-02-15 15:00 ` Toke Høiland-Jørgensen
2015-02-15 15:48 ` Sebastian Moeller
2015-02-15 15:56 ` Toke Høiland-Jørgensen
2015-02-15 16:12 ` Sebastian Moeller
2015-02-15 16:18 ` Toke Høiland-Jørgensen
2015-02-16 23:23 ` Sebastian Moeller
2015-02-15 16:33 ` Alan Jenkins
2015-02-16 9:05 ` Sebastian Moeller
2015-03-03 17:06 ` Sebastian Moeller
2015-03-03 21:23 ` Alan Jenkins
2015-03-03 21:27 ` Toke Høiland-Jørgensen
2015-03-03 21:35 ` Sebastian Moeller
2015-03-03 22:39 ` Alan Jenkins [this message]
2015-03-03 22:46 ` Sebastian Moeller
2015-02-15 16:16 ` 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=CANmMgnGc2pm7dRv4g_KRzg20vio9CZf1nykKy7qXFjhgi8Dm7Q@mail.gmail.com \
--to=alan.christopher.jenkins@gmail.com \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=moeller0@gmx.de \
/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