From owner-freebsd-bugs@freebsd.org  Wed Dec 27 22:32:17 2017
Return-Path: <owner-freebsd-bugs@freebsd.org>
Delivered-To: freebsd-bugs@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id 58647E82281
 for <freebsd-bugs@mailman.ysv.freebsd.org>;
 Wed, 27 Dec 2017 22:32:17 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from kenobi.freebsd.org (kenobi.freebsd.org
 [IPv6:2001:1900:2254:206a::16:76])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id 4669A7B948
 for <freebsd-bugs@FreeBSD.org>; Wed, 27 Dec 2017 22:32:17 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from bugs.freebsd.org ([127.0.1.118])
 by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id vBRMWGNw070425
 for <freebsd-bugs@FreeBSD.org>; Wed, 27 Dec 2017 22:32:17 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-bugs@FreeBSD.org
Subject: [Bug 224270] Get exit status of process that's piped to another: set
 -o pipefail is missing for /bin/sh
Date: Wed, 27 Dec 2017 22:32:17 +0000
X-Bugzilla-Reason: AssignedTo
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: Base System
X-Bugzilla-Component: bin
X-Bugzilla-Version: CURRENT
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: Affects Only Me
X-Bugzilla-Who: jilles@FreeBSD.org
X-Bugzilla-Status: New
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: ---
X-Bugzilla-Assigned-To: freebsd-bugs@FreeBSD.org
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-224270-8-55PE4M3fl0@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-224270-8@https.bugs.freebsd.org/bugzilla/>
References: <bug-224270-8@https.bugs.freebsd.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-BeenThere: freebsd-bugs@freebsd.org
X-Mailman-Version: 2.1.25
Precedence: list
List-Id: Bug reports <freebsd-bugs.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-bugs>,
 <mailto:freebsd-bugs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-bugs/>
List-Post: <mailto:freebsd-bugs@freebsd.org>
List-Help: <mailto:freebsd-bugs-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-bugs>,
 <mailto:freebsd-bugs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 27 Dec 2017 22:32:17 -0000

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D224270

--- Comment #5 from Jilles Tjoelker <jilles@FreeBSD.org> ---
The pipefail option was proposed for POSIX at
http://austingroupbugs.net/view.php?id=3D789 but this discussion seems to be
stalled. Apart from the SIGPIPE issue, it was pointed out that shell options
interact poorly with functions since they are dynamically scoped (for examp=
le,
  set -o pipefail; cmd1 | cmd2 | cmd3; r=3D$?; set +o pipefail
not only affects this pipe's exit status, but also everything done by cmd1,
cmd2 and cmd3 if they are functions). I will try to get this moving again.

However, the implementation of set -o pipefail is simple and doing without =
it
or a similar feature in scripts is complicated.

--=20
You are receiving this mail because:
You are the assignee for the bug.=