Kevin,
~/.bashrc is executed by bash for non-login shells, while if you
want to source global definitions, then you would want to include
something like this
if [ -f /etc/bashrc ]; then
. /etc/bashrc
fi
While /etc/bashrc sets the system-wide .bashrc file for interactive bash shells.
If you want to enable the settings (commands) in that file for login shells as
well, that file has to be sourced in /etc/profile (where you can add
additional paths - but I would definitely leave out the '.' in the
path statement)
This is how it works on Debian, I don't know about CentOS, but I will
check later this afternoon if you like.
On Mon, May 15, 2006 at 08:32:32AM -0400, Kevin Toppenberg wrote:
> So my question is, is there a way to make exportated variables
> "globals"? Also, how is everyone else doing this? Just put it in the
> .bashrc file?
>
--
Ismet B. Kursunoglu, MD, FCCP
Medical Director
Alaska Clinic, LLC
3750 E. Country Field Circle, STE B
Wasilla, Alaska 99654-6659
[EMAIL PROTECTED]
voice (907)357-7240
-------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Hardhats-members mailing list
Hardhats-members@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/hardhats-members
