From: Luk Claes <luk@debian.org>
To: Jim Rees <rees@umich.edu>
Cc: Steve Dickson <steved@redhat.com>, linux-nfs@vger.kernel.org
Subject: Re: [PATCH] start-statd: Use bash as -p is no POSIX
Date: Sat, 06 Aug 2011 15:11:07 +0200 [thread overview]
Message-ID: <4E3D3D6B.7050102@debian.org> (raw)
In-Reply-To: <20110806123858.GA20169@merit.edu>
On 08/06/2011 02:38 PM, Jim Rees wrote:
> Luk Claes wrote:
>
> sh -p is not guaranteed to be provided by POSIX shells. dash for instance
> does not provide this, so use bash explicitly.
>
> That's pretty funny. The script requires a posix shell, which bash isn't by
> default, so it provides an undocumented (in my ubuntu man page) option to
> force bash into compliance. Since the option itself isn't posix, we now
> require the use of this non-posix shell so we can guarantee posix
> compliance.
That would even be worse as the -p option in bash has *nothing* to do
with posix:
set -p's documentation in bash's manual:
Turn on privileged mode. In this mode, the
$ENV and $BASH_ENV files are not processed,
shell functions are not inherited from the
environment, and the SHELLOPTS, BASHOPTS,
CDPATH, and GLOBIGNORE variables, if they
appear in the environment, are ignored. If the
shell is started with the effective user
(group) id not equal to the real user (group)
id, and the -p option is not supplied, these
actions are taken and the effective user id is
set to the real user id. If the -p option is
supplied at startup, the effective user id is
not reset. Turning this option off causes the
effective user and group ids to be set to the
real user and group ids.
Cheers
Luk
next prev parent reply other threads:[~2011-08-06 13:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-06 9:59 [PATCH] start-statd: Use bash as -p is no POSIX Luk Claes
2011-08-06 12:38 ` Jim Rees
2011-08-06 13:11 ` Luk Claes [this message]
2011-08-29 16:05 ` Steve Dickson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4E3D3D6B.7050102@debian.org \
--to=luk@debian.org \
--cc=linux-nfs@vger.kernel.org \
--cc=rees@umich.edu \
--cc=steved@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).