On Mon, Sep 14, 2015 at 01:09:12AM +0200, Christian Tacke wrote:
Hi,
We (Knorrie, andi, and me) realized, that birdc outputs server errors to stdout much like normal server output.
Hi Thanks for the patch, you are right, not using stderr is probably an oversight.
There are a few aspects:
1. Is this useful? Hopefully. If you think this is a studpid idea, pleas explain!
I am not sure if stderr should be used even in interactive mode, but that is hopefully harmless.
2. Should this be the default (in an upcoming version)? I don't know, how many non humans depend on *all* output going to stdout and neglect stderr?
Probably in the next major version.
3. If the answer to (2) is "Need backward compatibility": Do we need some --enable-stderr then?
That seems unnecessary. -- Elen sila lumenn' omentielvo Ondrej 'Santiago' Zajicek (email: santiago@crfreenet.org) OpenPGP encrypted e-mails preferred (KeyID 0x11DEADC3, wwwkeys.pgp.net) "To err is human -- to blame it on a computer is even more so."