Date: Sat, 03 Feb 2018 14:23:38 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-rc@FreeBSD.org Subject: [Bug 190793] Some rc scripts return non zero status on success Message-ID: <bug-190793-4805-67Javtulfh@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-190793-4805@https.bugs.freebsd.org/bugzilla/> References: <bug-190793-4805@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=3D190793 Jilles Tjoelker <jilles@FreeBSD.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jilles@FreeBSD.org --- Comment #9 from Jilles Tjoelker <jilles@FreeBSD.org> --- (In reply to Devin Teske from comment #6) It is true that 'set -e' may be a factor with this kind of changes, but the= re are two factors which make it almost irrelevant here: * The functions in rc.subr are not supported with 'set -e' in effect. This applies both while sourcing /etc/rc.subr and while calling functions define= d in it. * 'set -e' only causes an immediate exit when an untested simple command, pipeline or subshell returns a non-zero exit status. One of the contexts considered "tested" is any command before && or ||. Therefore, a compound command false && true will not cause an immediate exit by itself, but onl= y if its non-zero exit status propagates to an outer function call, pipeline or subshell which is itself untested. --=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-190793-4805-67Javtulfh>