Output to stderr, but everything worked as planned

[Baptiste Daroussin]

On Wed, Apr 08, 2015 at 04:58:51PM +0200, Willem Jan Withagen wrote:
> Hoi,
> 
> I'm using this script (cronic) that uses the return-result of a program
> and possible output on stderr to decide wether a command has failed or
> not. If it has failed it sends the reporting on.
> 
> For pkg audit -F I get:
> ----
> Cronic detected failure or error output for the command:
> /usr/sbin/pkg audit -F
> 
> RESULT CODE: 0
> 
> ERROR OUTPUT:
> pkg: vulnxml file up-to-date
> 
> STANDARD OUTPUT:
> 0 problem(s) in the installed packages found.
> 
> ----
> 
> Which is sort of weird, since everything was oke.
> Is there any particular design behind writting these informationals to
> stderr??
> And/or would it not be better to write this to stdout?

You are right I'll fix that

Best regards,
Bapt
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 181 bytes
Desc: not available
URL: <http://lists.freebsd.org/pipermail/freebsd-pkg/attachments/20150409/ddec7989/attachment.sig>