Why is .bashrc getting read when executing a script

[vickey_20]

Hello
I have made a script with some errors in it. When I execute it the codes in .bashrc are getting executed , the message that i get when i first log in etc.....

[devils casper]

Post your script here.

[vickey_20]

Note: I executed this script on RHEL 4
-----------------------------------------------------------------------------------------------------------------------------------
File a
-----------------------------------------------------------------------------------------------------------------------------------

. b
echo $vadapav
echo hello
vashi
echo Back to a shell

-----------------------------------------------------------------------------------------------------------------------------------
File b
-----------------------------------------------------------------------------------------------------------------------------------

vadapav="newbombay"
vashi()
{
 echo   "Happy New Year"
}

-----------------------------------------------------------------------------------------------------------------------------------
.bashrc
-----------------------------------------------------------------------------------------------------------------------------------

# .bashrc
# User specific aliases and functions
alias rm='rm -i'
alias cp='cp -i'
alias mv='mv -i'
alias cls=clear
alias lg="cls;ls -gho"
# Source global definitions
if [ -f /etc/bashrc ]; then
	. /etc/bashrc
fi
n=/usr/notes/Essentials/
setterm -foreground green -store
sleep 1
cls
echo -e "\t\t\t\tWelcome Root"

-----------------------------------------------------------------------------------------------------------------------------------
How I executed the script

./a

[the_ultimate_samurai]

well not seeing the error i would imagine it has something to do with the fact that the variable "vadapav" is being declared in b, but then b is returning after the declaration, i dont think a variable declared in a shell stays declared after the shell exits. so when you call $vadapav the variable will be undefined...though an undefined variable will not cause an error...
of course vashi was also defined in b and would cease being defined in a when b returns. and this WOULD probably cause an error.
as for /etc/bashrc...i believe that gets executed whenever you run a shell, the statement #!/bin/bash is basically making this a sepperate shell within the shell, its running /bin/bash.
both b and a should do this if im not mistaken...

[vickey_20]

But when the other shell scripts I have executed successfully they don't execute my .bashrc. Also '.' operator is used to make another script run in the same script making the variable available in the script that called it.

[Rubberman]

Whenever a bash shell is started (this includes starting a script that is not executed inline with ". script" or "source script"), it sources ~/.bashrc - this is how the shell is designed. Other shells act the same was - csh -> .cshrc for example.

[i92guboj]

well not seeing the error i would imagine it has something to do with the fact that the variable "vadapav" is being declared in b, but then b is returning after the declaration, i dont think a variable declared in a shell stays declared after the shell exits. so when you call $vadapav the variable will be undefined...though an undefined variable will not cause an error...
of course vashi was also defined in b and would cease being defined in a when b returns. and this WOULD probably cause an error.

It's unrelated, but anyway, as the original posted said, the dot builtin actually dumps the contents of the second script in the shell where the first one is running. It's equivalent to the "source" command.

as for /etc/bashrc...i believe that gets executed whenever you run a shell, the statement #!/bin/bash is basically making this a sepperate shell within the shell, its running /bin/bash.
both b and a should do this if im not mistaken...

Whenever a bash shell is started (this includes starting a script that is not executed inline with ". script" or "source script"), it sources ~/.bashrc - this is how the shell is designed. Other shells act the same was - csh -> .cshrc for example.

Not exactly. The ~/.bashrc file should only be sourced when starting an interactive non-login shell. The key word is "interactive". The subshell that's spawned when you run a script is non-interactive, so ~/.bashrc shouldn't be sourced in this case. It isn't sourced on login shells either, in that case bash would look for ~/.bash_profile, ~/.bash_login and ~/.profile, in that order, and will source only the first one found, even if it's an empty file. The rest will be ignored.

I have no idea why would it be sourcing that file on a non-interactive subshell.

[the_ultimate_samurai]

hmm...i see...though according to the bash man page, if you do not include a / before the source it will check you path variable, so unless b is in his path im not sure it would execute it...
as for the bashrc...hmm...

a few things that could help:
the errors you get when it runs and either the contents of .bash_profile,.bash_login, or .profile whichever comes first.