I would like to know when you do a export PATH=$PATH: command, where is this being written? Also, how do you write it system wide? Just su, or do you have to log in as the root user? TIA Harry G
Harry G <harrycg@attbi.com> writes:
I would like to know when you do a export PATH=$PATH: command, where is this being written?
System wide: /etc/profile.local and /etc/csh.login.local, see /etc/profile and /etc/csh.login. Note that a process inherits the PATH environment variable from its parent and thus the setting will have no effect on processes already running. SuSE does not implement the traditional Unix approach and so it may take you some time to learn which files are sourced when a shell is started. Also, some processes may set their own PATH and thus ignore the setting in /etc/*.local. -- Alexandr.Malusek@imv.liu.se
Thanks so much! I don't understand, though why it is put in two different places. For example, does /etc/profile.local and /etc/csh.login.local both have to have the same entry? Or do different programs look in different files? Thanks again! Harry G On Sun December 8 2002 3:53 pm, Alexandr Malusek wrote:
Harry G <harrycg@attbi.com> writes:
I would like to know when you do a export PATH=$PATH: command, where is this being written?
System wide: /etc/profile.local and /etc/csh.login.local, see /etc/profile and /etc/csh.login.
Note that a process inherits the PATH environment variable from its parent and thus the setting will have no effect on processes already running. SuSE does not implement the traditional Unix approach and so it may take you some time to learn which files are sourced when a shell is started. Also, some processes may set their own PATH and thus ignore the setting in /etc/*.local.
Yes, the files are for different shells. bash, and sh use .profile (bash can also use .bashrc)... csh and tcsh use .cshrc and .login - Herman Harry G wrote:
Thanks so much! I don't understand, though why it is put in two different places. For example, does /etc/profile.local and /etc/csh.login.local both have to have the same entry? Or do different programs look in different files?
Thanks again!
Harry G
On Sun December 8 2002 3:53 pm, Alexandr Malusek wrote:
Harry G <harrycg@attbi.com> writes:
I would like to know when you do a export PATH=$PATH: command, where is this being written?
System wide: /etc/profile.local and /etc/csh.login.local, see /etc/profile and /etc/csh.login.
Note that a process inherits the PATH environment variable from its parent and thus the setting will have no effect on processes already running. SuSE does not implement the traditional Unix approach and so it may take you some time to learn which files are sourced when a shell is started. Also, some processes may set their own PATH and thus ignore the setting in /etc/*.local.
-- "DRM... Digitally Retarded Media - content that cannot reach its full potential because of artificial restraints."
* Herman Knief <herman@knief.net> [12-08-02 16:40]:
Yes, the files are for different shells. bash, and sh use .profile (bash can also use .bashrc)... csh and tcsh use .cshrc and .login
And, usually, the ones under /etc/ are system-wide, ie: all users, and the ones for you personally are dot-files (.bashrc, .profile, ...) and are in your home directory, ie: /home/your-name/ or ~/. -- Patrick Shanahan Registered Linux User #207535 @ http://counter.li.org icq#173753138
participants (4)
-
Alexandr Malusek -
Harry G -
Herman Knief -
SuSEnixER