* Why does crushtool send all it's output to stderr?
@ 2014-07-17 20:59 Wido den Hollander
2014-07-17 21:06 ` Sage Weil
0 siblings, 1 reply; 2+ messages in thread
From: Wido den Hollander @ 2014-07-17 20:59 UTC (permalink / raw)
To: ceph-devel
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
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: Why does crushtool send all it's output to stderr?
2014-07-17 20:59 Why does crushtool send all it's output to stderr? Wido den Hollander
@ 2014-07-17 21:06 ` Sage Weil
0 siblings, 0 replies; 2+ messages in thread
From: Sage Weil @ 2014-07-17 21:06 UTC (permalink / raw)
To: Wido den Hollander; +Cc: ceph-devel
On Thu, 17 Jul 2014, Wido den Hollander wrote:
> 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?
Nope! There's a lot that could be improved here from a UX standpoint, I
think. :)
sage
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2014-07-17 21:06 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2014-07-17 20:59 Why does crushtool send all it's output to stderr? Wido den Hollander
2014-07-17 21:06 ` Sage Weil
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.