[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: "source" shell commands

From: Matthew Flaschen
Subject: Re: "source" shell commands
Date: Sun, 25 Mar 2007 06:55:36 -0400
User-agent: Thunderbird (X11/20070306)

Peter Dyballa wrote:
> Am 25.03.2007 um 01:08 schrieb Matthew Flaschen:
>> Since I only really need JAVA_HOME, I'm just setting that manually with
>> setenv.
> All you need to do, is to make sure that when you log-in this
> environment variable gets set. In case of (t)csh it's simple:
> /etc/csh.login is probably read, otherwise ~/.login. In case of bash it
> is more complicated since bash also checks whether this shell is
> interactive or not, to be a login shell is not the only criterion. You
> could think of putting JAVA_HOME into /etc/.profile or into /etc/.bashrc
> or both – or into your private versions ~/.profile and/or ~/.bashrc.
> JAVA_HOME probably is an environment variable that is not specific to
> some user but is of system-wide meaning.
> You can check with ps or better pstree (pstree -p $$) how you logged in.

Apparently bash.  However, ~/.bashrc already sources ~/.rc , which
includes JAVA_HOME .  It was my impression that bash *always* read
~/.bashrc .  Should I source ~/.rc in ~/.profile instead?

Matthew Flaschen

reply via email to

[Prev in Thread] Current Thread [Next in Thread]