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, <[email protected]> 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 _______________________________________________ Cerowrt-devel mailing list [email protected] https://lists.bufferbloat.net/listinfo/cerowrt-devel
