OK, my apologies, i answered without enough thinking:
the PATH should be set in profile or .profile or .bash_profile because it
will be initialized only once (login) and will be kept through all jobs
as it is exported (export PATH).
if it is defined in bashrc or .bashrc, and it is just appending things
(PATH=$PATH:/my/new/dir) then this new directory wil be appended to the
PATH variable several times (each time a bash is launched it will get the
PATH from its father and append the new dir to it).
so bashrc should be used to put aliases
PATH should be defined once in profile during login process.
pascal.
-----Original Message-----
From: michael jones [SMTP:[EMAIL PROTECTED]]
Sent: Friday, April 16, 1999 9:29 PM
To: [EMAIL PROTECTED]
Cc: LENGARD Pascal OCISI; Linux Newbie; Shane McKeown; Linux
Networking
Subject: Re: Setting PATH
[EMAIL PROTECTED] wrote:
> LENGARD Pascal OCISI dixit:
> ~> the PATH should be set in /etc/bashrc for system wide definition and
in
> ~> ~/.bashrc for single user definition.
>
> Actually, /etc/profile is for system wide definition, while
~/.bash_profile
is
> for the login shell, and ~/.bashrc is for an interactive shell.
There's no
> /etc/bashrc on my system (Debian 2.0).
yeah Debian must be different,
in Red Hat there is a /etc/bashrc. it is for system wide, the ~/.bashrc
is for
user define. i use the /etc/bashrc for alias definitions and the
/etc/profile
for the PATH. i don't know why, someone told me to do it that way in
Red Hat and it works. if i am wrong i would like to know.
>
>
> Regards
>
> Horacio
> --
> Claves - GnuPG/PGP - Keys : http://www.rediris.es/cert/keyserver
> o/or
> Env�a un mensaje vac�o a [EMAIL PROTECTED] con la l�nea de asunto:
> Send a blank message to [EMAIL PROTECTED] with the subject line:
> Tipo de Clave/Key Type Asunto:/Subject:
>
> DSA/ElGamal fetch dsa/elgamal
> DSS/Diffie-Hellman fetch dh/dss
> RSA fetch rsa
--
michael jones * erleichda archiving * usa
this space for rent.
