[Bug 589496] Re: bash --rcfile does not behave as documented
MestreLion
launchpad at rodrigosilva.com
Wed Feb 1 04:15:52 UTC 2012
Debian bug #516152 is from 2009, and #343673 from 2006 ... none of them
are fixed, so I don't think they care.
This is not an irrelevant package we are talking about, its a flaw in
invocation of something critical like bash. Is there any chance this
could be patched ASAP in Ubuntu and then the patch submitted to Debian
afterwards?
Also, this is not only a bug in documentation as #516152 and #343673
suggests: with current behaviour, it's impossible to "disable" the
execution of /etc/bash.bashrc and still give the user a choice of
executing a personal rcfile.
Samples:
$ cat /etc/bash.bashrc
echo etcbashrc
$ cat ~/customrc
echo customrc
$ cat ~/.bashrc
echo bashrc
$ bash
etcbashrc
bashrc
$ bash --rcfile ~/customrc
etcbashrc
customrc
$ bash --norc --rcfile ~/customrc
$
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to bash in Ubuntu.
https://bugs.launchpad.net/bugs/589496
Title:
bash --rcfile does not behave as documented
Status in “bash” package in Ubuntu:
Confirmed
Status in “bash” package in Debian:
New
Bug description:
Binary package hint: bash
the bash manpage says this about --rcfile
--rcfile file
Execute commands from file instead of the system wide initial‐
ization file /etc/bash.bashrc and the standard personal initial‐
ization file ~/.bashrc if the shell is interactive (see INVOCA‐
TION below).
under INVOCATION it says
When an interactive shell that is not a login shell is started, bash
reads and executes commands from /etc/bash.bashrc and ~/.bashrc, if
these files exist. This may be inhibited by using the --norc option.
The --rcfile file option will force bash to read and execute commands
from file instead of /etc/bash.bashrc and ~/.bashrc.
but when i execute
$ bash --rcfile somercfilewhichreallydoesexistandisreadableandall
it will still read /etc/bash/bashrc (can be verified by adding --verbose)
using lucid with bash 4.1-2ubuntu3
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bash/+bug/589496/+subscriptions
More information about the foundations-bugs
mailing list