Date: Thu, 9 Apr 2015 02:04:20 +0200 From: Baptiste Daroussin <bapt@FreeBSD.org> To: Willem Jan Withagen <wjw@digiware.nl> Cc: freebsd-pkg@freebsd.org Subject: Re: Output to stderr, but everything worked as planned Message-ID: <20150409000420.GA54379@ivaldir.etoilebsd.net> In-Reply-To: <5525422B.4000900@digiware.nl> References: <5525422B.4000900@digiware.nl>
next in thread | previous in thread | raw e-mail | index | archive | help
--vkogqOf2sHV7VnPd Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Apr 08, 2015 at 04:58:51PM +0200, Willem Jan Withagen wrote: > Hoi, >=20 > 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. >=20 > For pkg audit -F I get: > ---- > Cronic detected failure or error output for the command: > /usr/sbin/pkg audit -F >=20 > RESULT CODE: 0 >=20 > ERROR OUTPUT: > pkg: vulnxml file up-to-date >=20 > STANDARD OUTPUT: > 0 problem(s) in the installed packages found. >=20 > ---- >=20 > 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 --vkogqOf2sHV7VnPd Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iEYEARECAAYFAlUlwgQACgkQ8kTtMUmk6ExS5wCfY4MY29nUoE0Zulvi8xSdxsoF I2sAoKluySxoLZ1Lk4rvb0nfpZsfHM51 =tZNk -----END PGP SIGNATURE----- --vkogqOf2sHV7VnPd--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20150409000420.GA54379>