From: Dave Taht <dave.taht@gmail.com>
To: Valdis Kletnieks <Valdis.Kletnieks@vt.edu>
Cc: "cerowrt-devel@lists.bufferbloat.net"
<cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] how is everyone's uptime?
Date: Thu, 11 Dec 2014 16:22:15 -0800 [thread overview]
Message-ID: <CAA93jw5wcY_VTYPRZpKioOQMH4FXc_mPFR_xRwq7p=_Z=+J2Ag@mail.gmail.com> (raw)
In-Reply-To: <28587.1418343489@turing-police.cc.vt.edu>
well, you would have crashed mysteriously in another 3-4 weeks anyway,
given the growth there. :/
One of the things that bothers me about all the folks trying to use
debian for embedded use is that they don't fix syslogging in general,
and thus a crash is merely a matter of time and flash space.
In embedded, we care a lot about slow memory leaks, and things like
logfiles growing out of control, and openwrt takes care of most of
that for you. But not all of it. You want zero memory growth,
transparent restarts of all daemons from crashes, etc....
I am also increasingly impressed by what the low memory footprint of
openwrt does for you. Even on the rangeley (with 2MB cache) it seems
tons faster and more resistant to temporary glitches to have such a
small working set.
I am thinking a lot of the work that opendaylight, etc, is wasted,
they should just be running a smaller OS....
On Thu, Dec 11, 2014 at 4:18 PM, <Valdis.Kletnieks@vt.edu> wrote:
> On Thu, 11 Dec 2014 13:50:44 -0800, Dave Taht said:
>
>> > root@bogon-gateway-1:~# wc /tmp/log/babeld.log
>> > 772310 6176740 49416530 /tmp/log/babeld.log
>> > root@bogon-gateway-1:~# sort /tmp/log/babeld.log | uniq -c
>> >
>> > Oh kewl. That seems to have killed it :)
>> >
>> > Uptime is now 11 minutes, and the log is much shorter.
>>
>> Heh. Sorry!
>
> Not your fault. I don't think the design specs included "have enough
> ram/swap to sort a 3/4 million line logfile" :)
>
> More importantly, it rebooted cleanly and without hiccupping any
> connections through it.
--
Dave Täht
thttp://www.bufferbloat.net/projects/bloat/wiki/Upcoming_Talks
next prev parent reply other threads:[~2014-12-12 0:22 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-10 22:52 Dave Taht
2014-12-11 19:58 ` Valdis.Kletnieks
2014-12-11 21:50 ` Dave Taht
2014-12-12 0:18 ` Valdis.Kletnieks
2014-12-12 0:22 ` Dave Taht [this message]
2014-12-12 0:32 ` Aaron Wood
2014-12-12 0:42 ` Dave Taht
2014-12-12 7:33 ` [Cerowrt-devel] an option for a new platform? Erkki Lintunen
2014-12-12 14:52 ` Dave Taht
2014-12-13 23:02 ` David P. Reed
2014-12-16 9:02 ` Dave Taht
2014-12-12 1:30 ` [Cerowrt-devel] how is everyone's uptime? Joseph Swick
2014-12-12 1:52 ` Jim Gettys
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='CAA93jw5wcY_VTYPRZpKioOQMH4FXc_mPFR_xRwq7p=_Z=+J2Ag@mail.gmail.com' \
--to=dave.taht@gmail.com \
--cc=Valdis.Kletnieks@vt.edu \
--cc=cerowrt-devel@lists.bufferbloat.net \
/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