All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wido den Hollander <wido@42on.com>
To: ceph-devel <ceph-devel@vger.kernel.org>
Subject: Why does crushtool send all it's output to stderr?
Date: Thu, 17 Jul 2014 22:59:09 +0200	[thread overview]
Message-ID: <53C8391D.8020300@42on.com> (raw)

Hi,

When running tests on a crushmap with crushtool it noticed that all 
output is send to stderr, for example:

$ crushtool -i cm --test --rule 4 --num-rep 3 --show-statistics

All the output goes to stderr while I think stdout would be a better place.

Any good reason for this?

-- 
Wido den Hollander
42on B.V.
Ceph trainer and consultant

Phone: +31 (0)20 700 9902
Skype: contact42on

             reply	other threads:[~2014-07-17 20:59 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-17 20:59 Wido den Hollander [this message]
2014-07-17 21:06 ` Why does crushtool send all it's output to stderr? Sage Weil

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=53C8391D.8020300@42on.com \
    --to=wido@42on.com \
    --cc=ceph-devel@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.