[Bug 1337944] [NEW] output of service --status-all written neither to stdout nor stderr

[Karl-Philipp Richter]

Public bug reported:

The output of `sudo service --status-all` is written neither to stdout,
nor stderr as shown by failing piping of command output, e.g. `sudo
service --status-all 2> /dev/null 1> /dev/null` still writes to
terminal. This is unnecessary and prevents easy usage of tools like
`grep`, `less`, etc. and furthermore undocumented.

experienced with version `service ver. 0.91-ubuntu1` on Ubuntu 14.04

** Affects: sysvinit (Ubuntu)
     Importance: Undecided
         Status: New

** Description changed:

  The output of `sudo service --status-all` is written neither to stdout,
  nor stderr as shown by failing piping of command output, e.g. `sudo
  service --status-all 2> /dev/null 1> /dev/null` still writes to
- terminal.
+ terminal. This is unnecessary and prevents easy usage of tools like
+ `grep`, `less`, etc. and furthermore undocumented.
  
  experienced with version `service ver. 0.91-ubuntu1` on Ubuntu 14.04

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to sysvinit in Ubuntu.
https://bugs.launchpad.net/bugs/1337944

Title:
  output of service --status-all written neither to stdout nor stderr

Status in “sysvinit” package in Ubuntu:
  New

Bug description:
  The output of `sudo service --status-all` is written neither to
  stdout, nor stderr as shown by failing piping of command output, e.g.
  `sudo service --status-all 2> /dev/null 1> /dev/null` still writes to
  terminal. This is unnecessary and prevents easy usage of tools like
  `grep`, `less`, etc. and furthermore undocumented.

  experienced with version `service ver. 0.91-ubuntu1` on Ubuntu 14.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sysvinit/+bug/1337944/+subscriptions