Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Jim Gettys <jg@freedesktop.org>
To: Dave Taht <dave.taht@gmail.com>
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 20:52:29 -0500	[thread overview]
Message-ID: <CAGhGL2CsGX7-j0HHzj7Sus2sHveDuVqxdzAdwiAstbxP-XXBpA@mail.gmail.com> (raw)
In-Reply-To: <CAA93jw6mJ=n2HkrgmG=y21BC5HGYH6-OAr2SEL9zp_uACpsmnQ@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1562 bytes --]

root@router:~# uptime
 17:31:25 up 131 days,  4:03,  load average: 0.23, 0.08, 0.06
root@router:~# df
Filesystem           1K-blocks      Used Available Use% Mounted on
rootfs                    7296       416      6880   6% /
/dev/root                 7680      7680         0 100% /rom
tmpfs                    63128      5992     57136   9% /tmp
/dev/mtdblock5            7296       416      6880   6% /overlay
overlayfs:/overlay        7296       416      6880   6% /
tmpfs                      512         0       512   0% /dev
oot@router:~# free
             total         used         free       shared      buffers
Mem:        126256        66224        60032            0         6572
-/+ buffers:              59652        66604
Swap:            0            0            0




On Wed, Dec 10, 2014 at 5:52 PM, Dave Taht <dave.taht@gmail.com> wrote:
>
> the lab where I was keeping a box up under load had a long enough
> power failure last week to keeelll my approximatively 76 days uptime.
>
> Anybody else got any record-holders here?
>
> I am interested in long term memory leakage (run a free),
> process usage (runaways like pimd), and growth in disk space usage (df),
> so output like
>
> uptime
> free
> df
>
> periodically would be nice.
>
> --
> Dave Täht
>
> http://www.bufferbloat.net/projects/bloat/wiki/Upcoming_Talks
> _______________________________________________
> Cerowrt-devel mailing list
> Cerowrt-devel@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/cerowrt-devel
>

[-- Attachment #2: Type: text/html, Size: 2973 bytes --]

      parent reply	other threads:[~2014-12-12  1:52 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
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 [this message]

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=CAGhGL2CsGX7-j0HHzj7Sus2sHveDuVqxdzAdwiAstbxP-XXBpA@mail.gmail.com \
    --to=jg@freedesktop.org \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=dave.taht@gmail.com \
    /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