Date: Sun, 07 Jan 2018 17:55:15 +0000 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 Message-ID: <bug-224270-8-y7kx6V0rU9@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/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D224270 Wolfram Schneider <wosch@FreeBSD.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|New |Open --- Comment #6 from Wolfram Schneider <wosch@FreeBSD.org> --- Hi Jilles, thanks for the pointer to the POSIX discussion. We should be compatible with the /bin/bash. BASH is the industry standard f= or shell scripts, unfortunately. For me the only reason to use the bash is the pipefail option. I wish I could replace the first line #!/bin/bash with #!/bin/sh and everything works as expected. Regarding the implementation: the POSIX issue mention in the Description section that =E2=80=9Cbusybox sh=E2=80=9D has the feature implemented. busy= box is using the ash, re-ported from NetBSD and debianized. I don=E2=80=99t think we can use= the code from ash due the GPL licence, but we could use some of the busybox regressi= on tests (./ash_test/ash-misc/pipefail.*) to make sure that our implementation runs fine. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-224270-8-y7kx6V0rU9>