From owner-freebsd-pkg@FreeBSD.ORG Thu Apr 9 00:04:26 2015 Return-Path: Delivered-To: freebsd-pkg@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 1804462B for ; Thu, 9 Apr 2015 00:04:26 +0000 (UTC) Received: from mail-vn0-x236.google.com (mail-vn0-x236.google.com [IPv6:2607:f8b0:400c:c0f::236]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id BB471E19 for ; Thu, 9 Apr 2015 00:04:25 +0000 (UTC) Received: by vnbg7 with SMTP id g7so17885040vnb.11 for ; Wed, 08 Apr 2015 17:04:24 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:date:from:to:cc:subject:message-id:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; bh=8N5GwUIR7qdGsRpu2AQfEq/MXLZga/M8KVJeT8zUwuk=; b=nVMOVsGmTXCmyih4rsdN/Bk6e/xvhlp08e6ZstaXli2wpIn1O/Zs+GKOzZ5DNs/y9b O3iwEknMnIKob8sm9rSTDjECpY7G08vD1RU+R5Mp1JivZUJF6gGHJKeI47/eaox5E0Pn +Nu0umE6Iy7qiQZHChL7NPDrpA9WpckdrXo9Sa2l3NfjY5KlcbKI6YMjBZSjEwUZDomD PPye8oCkL1fhr5WviNCy2p196KJiB/ezKDCbHFoWmFIh7INzSE5Xuvp7avfsXbuQ2htT gwGGqHlSVRuaBKTlzqJdJQFkMWaGtNJ/za7WEF3ZC7iPhKBddtuU/xIFtQdOGobKTKFU GAaQ== X-Received: by 10.52.183.68 with SMTP id ek4mr19748245vdc.59.1428537864786; Wed, 08 Apr 2015 17:04:24 -0700 (PDT) Received: from ivaldir.etoilebsd.net ([2001:41d0:8:db4c::1]) by mx.google.com with ESMTPSA id ad5sm2322051vdc.13.2015.04.08.17.04.22 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 08 Apr 2015 17:04:23 -0700 (PDT) Sender: Baptiste Daroussin Date: Thu, 9 Apr 2015 02:04:20 +0200 From: Baptiste Daroussin To: Willem Jan Withagen Subject: Re: Output to stderr, but everything worked as planned Message-ID: <20150409000420.GA54379@ivaldir.etoilebsd.net> References: <5525422B.4000900@digiware.nl> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="vkogqOf2sHV7VnPd" Content-Disposition: inline In-Reply-To: <5525422B.4000900@digiware.nl> User-Agent: Mutt/1.5.23 (2014-03-12) Cc: freebsd-pkg@freebsd.org X-BeenThere: freebsd-pkg@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Binary package management and package tools discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 09 Apr 2015 00:04:26 -0000 --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--