Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Rich Brown <richb.hanover@gmail.com>
To: "R." <redag2@gmail.com>
Cc: cerowrt@lists.bufferbloat.net,
	cerowrt-devel <cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] [Bug #442] status?
Date: Sat, 16 Aug 2014 23:09:24 -0400	[thread overview]
Message-ID: <4F06D963-629B-42AA-B87A-FF556AF4BFFF@gmail.com> (raw)
In-Reply-To: <CACj-SW21Fen4LJbKeNAwma82cbiVWX39PZrh-hytp7FBTujgnw@mail.gmail.com>

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


> I will try to keep an eye and report back. You know what would be
> really useful? A breakdown of all the useful logs that one would need
> to provide when reporting on a bug.
> 
> Even more user-friendly would be a script that generates all relevant
> information/logs to debugging. Perhaps one day? :)

Check the cerostats.sh script that's in /usr/lib/CeroWrtScripts for recent CeroWrt builds. That collects a number of interesting stats and puts them in /tmp/cerostats_output.txt

Rich

[-- Attachment #2: Message signed with OpenPGP using GPGMail --]
[-- Type: application/pgp-signature, Size: 496 bytes --]

      reply	other threads:[~2014-08-17  3:09 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-16 18:23 Dave Taht
2014-08-16 18:55 ` Daniel Ezell
2014-08-16 19:07   ` R.
2014-08-16 22:32     ` Sebastian Moeller
2014-08-16 23:53       ` R.
2014-08-17  3:09         ` Rich Brown [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=4F06D963-629B-42AA-B87A-FF556AF4BFFF@gmail.com \
    --to=richb.hanover@gmail.com \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=cerowrt@lists.bufferbloat.net \
    --cc=redag2@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