From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-ob0-x230.google.com (mail-ob0-x230.google.com [IPv6:2607:f8b0:4003:c01::230]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by huchra.bufferbloat.net (Postfix) with ESMTPS id 2839321F543 for ; Thu, 11 Dec 2014 16:22:16 -0800 (PST) Received: by mail-ob0-f176.google.com with SMTP id vb8so5754275obc.7 for ; Thu, 11 Dec 2014 16:22:16 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=/7jUkOm4h39ngZo1kHh+f9dATTFlzwnMpqysU/Z/+CE=; b=DAanoEgGkqAr8L7Venz+1qhz3Hv7+oab5Y6ci0vRGNqqBdwNRWptckpfkdfVUMICnj h4eGpiLzC7Bors4Xodf13WUZPSMW9nN9xZeAK8CE+D1anli2PKZ3ufG6jXYz11P/Bfy5 uY1rbS2Qkh+DkcltlbetEJJIuLC6Kt4+b3Xf0QMut8ijR91jBZOts4hITJXHIlZ3xYtE Em22nwd6eBqE7UoLcFwoS8sWc0k1gufm+lUccnIR6WQp1rhHrMsRZfGaqzBHrKFZJIq6 Tg6IRiynAvlvnqwnzaOeczUpDyB1p0DMosIAvyWmx4SXdeEPWHvTYUTehb2gnomD7oJa +zxQ== MIME-Version: 1.0 X-Received: by 10.182.241.133 with SMTP id wi5mr8322171obc.10.1418343735930; Thu, 11 Dec 2014 16:22:15 -0800 (PST) Received: by 10.202.227.77 with HTTP; Thu, 11 Dec 2014 16:22:15 -0800 (PST) In-Reply-To: <28587.1418343489@turing-police.cc.vt.edu> References: <16381.1418327937@turing-police.cc.vt.edu> <28587.1418343489@turing-police.cc.vt.edu> Date: Thu, 11 Dec 2014 16:22:15 -0800 Message-ID: From: Dave Taht To: Valdis Kletnieks Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Cc: "cerowrt-devel@lists.bufferbloat.net" Subject: Re: [Cerowrt-devel] how is everyone's uptime? X-BeenThere: cerowrt-devel@lists.bufferbloat.net X-Mailman-Version: 2.1.13 Precedence: list List-Id: Development issues regarding the cerowrt test router project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 12 Dec 2014 00:22:45 -0000 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, 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. --=20 Dave T=C3=A4ht thttp://www.bufferbloat.net/projects/bloat/wiki/Upcoming_Talks