Bug #4944

Command output

Added by Konstantinos Tompoulidis over 10 years ago. Updated over 10 years ago.

Status:Assigned Start date:01/17/2014
Priority:Medium Due date:
Assignee:Christos Stavrakakis % Done:


Category:- Spent time: -
Target version:-



It seems that the output of some commands goes to stderr instead of stdout.

It would be great if only errors went to stderr and everything else (?) went to stdout.

  • I have assigned this to Vangelis to route it properly. I cannot be really sure where this applies.


#1 Updated by Vangelis Koukis over 10 years ago

The rule is: all diagnostics go to stderr (not just errors, warnings, and progress reports too),
and all expected/useful output (tables, lists) goes to stdout.

Could you please name a command which violates this, so we know where to start?

#2 Updated by Vangelis Koukis over 10 years ago

  • Status changed from New to Assigned
  • Assignee changed from Vangelis Koukis to Christos Stavrakakis

#3 Updated by Konstantinos Tompoulidis over 10 years ago

We had noticed it a few months back but we did not keep track.
It must have been dealt with internally.

We noticed it again today using "snf-manage enforce-resources-cyclades"

We had a brief discussion with gkorf about this.
He suggested to open a ticket in order to check if this applies to other sub-commands as well.

Also available in: Atom PDF