Path: csiph.com!goblin1!goblin.stu.neva.ru!usenet.stanford.edu!not-for-mail From: Eli Schwartz Newsgroups: gnu.bash.bug Subject: Re: How to tell Bash multiple values are success? Date: Wed, 19 Jun 2019 11:14:37 -0400 Lines: 99 Approved: bug-bash@gnu.org Message-ID: References: NNTP-Posting-Host: lists.gnu.org Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="u7yYgnae4bPY2cVKX2kisIc78fL4fM78x" X-Trace: usenet.stanford.edu 1560957301 21838 209.51.188.17 (19 Jun 2019 15:15:01 GMT) X-Complaints-To: action@cs.stanford.edu To: bug-bash@gnu.org Envelope-to: bug-bash@gnu.org DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=archlinux.org; s=orion; t=1560957281; bh=vrX8cFKE466kXK1NXfLBcJh7U6RItrHkNKApO9oxZzc=; h=Subject:To:References:From:Date:In-Reply-To; b=n8a3VuhskELmvapMU6g8TFDQbzDOQx6Q3hdguVUq263MyQ1rAzZcg9hdaboZ0TK9o jBalgulQ/XOkYKjljLRDBt4KYlftrHNGpq8+Ahm2tzIn4A/FF6C7gdr7fYiml5uz+j mNrPi2asI47rupkQNQMjFBFTds1eLmLc/5IqQt49064bV+WEMd9E1gC0+XLCzXBs7l R5LcsDhVLVbJDlDQzvKX/PK+1v2+7kwnBMF/6NzHdCma1Rs+j9OEpvExsRqsfirbHb H15rNwBY5Dw5ap+hOL3Dja+OV6tK7WkEIoLshDQWGFLQ1DhGApvI897WD0cQ0eEoch MVyLlXP/ebYA3xJV4PzeJk5Ctpl7R6Mj5gu/GsLJdhKhO4ExlCL3rEdyw/69DXqzUK jKdIhEU5iVyvePiBL6pQ1YGArKy/+JlTA1nZIsHNiuYjZhefBwjwOqUgXttWrRMn7B zBk9It79DJBekPI4Sap7JtQ8Um+uzipvmCM69XIBt3O/2elkRhjdzCBYNWJsdNuo1t m62a9n3o1QPLeBvy8QTykRt+AS8r5uli6Nwx0jNz0YFeQ9GQ00J99T0GTWjEFEpR6C uq2q2e7UjqJF/jNm60yDxYIeV9RgA/tIkU09ZdFz1gIYTm0W60hXlZOtUH91vLxbC0 Ac46sDJ2yb4CmmXDGJ6b2zxE= Openpgp: preference=signencrypt X-Clacks-Overhead: GNU Terry Pratchett User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.7.1 In-Reply-To: X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 88.198.91.70 X-BeenThere: bug-bash@gnu.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Bug reports for the GNU Bourne Again SHell List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-Mailman-Original-Message-ID: X-Mailman-Original-References: Xref: csiph.com gnu.bash.bug:15063 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --u7yYgnae4bPY2cVKX2kisIc78fL4fM78x Content-Type: multipart/mixed; boundary="x6M8wBaYap2jSVrlwcEiNx1MocVmRLoHs"; protected-headers="v1" From: Eli Schwartz To: bug-bash@gnu.org Message-ID: Subject: Re: How to tell Bash multiple values are success? References: In-Reply-To: --x6M8wBaYap2jSVrlwcEiNx1MocVmRLoHs Content-Type: text/plain; charset=utf-8 Content-Language: en-US-large Content-Transfer-Encoding: quoted-printable On 6/19/19 11:01 AM, Jeffrey Walton wrote: > Hi Everyone, >=20 > I have a systemd service that automatically applies updates. Looking > at the service history, the service reports failure when it installs > updates due to this: >=20 > if dnf -y update &>/dev/null > then > echo "Upgraded system" > else > echo "Failed to upgrade system" > exit 1 > fi >=20 > The problems seems to be 0, 100 and 200 are success. When updates are > installed either 100 or 200 is returned. Confer, > https://dnf.readthedocs.io/en/latest/command_ref.html . >=20 > I looked through Bash Variables, but I did not see a way to signal the > information to Bash. Confer, > https://www.gnu.org/software/bash/manual/html_node/Bash-Variables.html > . >=20 > How do I tell Bash 0, 100 and 200 are success? (Or, how to tell Bash 1 > is the only failure?) Neither 100 nor 200 are successes, and the page you linked explains exactly why. The former is only relevant to the subcommand "dnf check-update" and indicates that your system is *not* fully upgraded and you should fix tha= t. The latter indicates that you successfully updated the system, but potentially bad things occurred in the process. You can choose to *ignore* selected errors, however, using Greg's suggestion. There is no option to make bash dramatically redefine its entire internal understanding of how basic unix return codes work. --=20 Eli Schwartz --x6M8wBaYap2jSVrlwcEiNx1MocVmRLoHs-- --u7yYgnae4bPY2cVKX2kisIc78fL4fM78x Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAEBCgAdFiEEvSewel70XCra9w4EhIGKaBmvSpsFAl0KUV0ACgkQhIGKaBmv SpswPxAA2dT0cnskmY1gCGbhZ/obivzGM0MD8SgSuIP8oGEd6yJpmI+Ec18eUWdk MljfR/MxhfLNkqFLpHq0fnMDDzADFmsSqm1OeggICJ7d6zbOGgyfLpQJItxUuE79 uNBgGTJysw6JMJuV4glFuYVm85z49J+dPehhIYGCYvirmRmcgkLiiQv7/jYnrMGc dZofZu0J+J8Ol9CGGVIl0bslzsEfUUz0T3vZinfk++Vjzd0OB/Tj3GJSacqWRhrs X67BGNonY4m4hMHsw01tXpEdSLu9r8SPWYYPxRJscp2IwfnZ3j+ggZZYk4ghylv2 UfJjSaPTH9W0deJ/z8DIkosFa/yEffQ+EFHDcVjLE+nZPDVDdgmrE7q2bWf48JSL PWnzWeea+X3FBDdD85qISODXmvqOdgpZ+V4dCABGqWgqOB9EjDuh3Gx8+H4UcrlY gtsJjgEw0an7V+F39HAzPyShwSE18bIrP16u4+lCJL6aFAv2V47c73+B6AysPkdq 4hNSrfQvuxGK/ulzaMfdPE4iXqLxe8RQhWd72xlCcCcXRLVStCNAw78lXSMO55u6 Zv2LaVvMp6Jt5sSb/JXiICI6+Lw9flDWxlRdgWMe5Td7Txu+vIRKgpEN1MptKlHX 9ndohQeyU2te0xLeEO1W2BTMs6MUm+E3BHnPGkxoDUJhY9bmKemJAjMEAQEKAB0W IQRgQRMEwJ02YoNA7v/OsWfvtXIr1gUCXQpRXQAKCRDOsWfvtXIr1oIuD/9RSksv g+n8AU4lX5qKHF4x5zS722rio6wSj8OMIgJR8WuxNSkNbk7jaYWu1iYYKgCCMPG1 s4o5Sf9/se0AXV4qpNxOqDHsp6CGA166JjjuwWvDf6n2WOniN8QrPkSd/W4bVBfy AzcxfbOueQEryi+kmzxEmQDe49RAD5RcVQ9rUz9GSbELjQUZdidD7fGTrVxyQZRN 2XABDAJEOIx57bxDd9BHgPEHVUUHuRXhEiCIm+sKylEFrmVcohyJKZtPRh+Sx/Np GZYq4y974INRAmxRanVAzipq2bhMsaLvJBIKhcGQ/rlkEUIOeYZIyHNPld1z9gX/ BU3BDK/VcAkz3ifPaTH9cFM9QPsdxyMj4SsqI+ua+zYdXefzcHuCVgLSai/+Bypj rfGuJiXWrWdLkmADX34eJ1NxUGxfbqwxiJ1KghMWmPmfFRtUFeG7zdAfP5uGGc5L pgccait2JVdstQQnZ23rUQXNSSN1LxUsf3ZjEh4DAqKq6RJUeGwDwkLGdFIlKtm1 4VGAFSI+F/MR9HpJhdKgEa8W7XdNlag/AhcgKAN+p+a8Fy/Wf8+uJa6vmCWQdGw6 zu3EjmvqsZZ1esrN81PIBneetVP6lxwerMG496w5EQAvizq2uSHn9g30WHNxKtrb hQq5y1r7HBlC7GfWaMDevInOjDn1Gyb6Fj684w== =XX0H -----END PGP SIGNATURE----- --u7yYgnae4bPY2cVKX2kisIc78fL4fM78x--