Login Profile

jonty_11 · 10-27-2004, 06:06 PM

Which file do I have to change for a user to have his LD_LIBRARY_PATH and PATH variables set automatically when he logs in....
.bash_profile doesnt work
.bashrc doesnt work......

Is there any other file.....

amfoster · 10-27-2004, 09:27 PM

Either should work as long as your user is indeed using the bash shell.

You are setting the path like this right?

export PATH=$PATH:newdir:another/new/dir etc etc

tonyfreeman · 10-27-2004, 11:16 PM

I have a system where users use different shells ... there are two files that get read by all of them: .login and .profile. If your users do not have a .login file or a .profile then the system defaults are located in /etc/login and /etc/profile .... you can set the environmental variables in the system wide login/profile files or you can simply create the the user .login/.profile files in the user's home directory.

-- Tony

jonty_11 · 10-28-2004, 12:51 PM

AMFOSTER: yes i am setting path just like that....

Tony: I was able to do it within the .bashrc file finally.....

But how does the system know which file to use....if I were to create a .login file for my user...will that be used or will .bashrc be used...

Tinkster · 10-28-2004, 02:45 PM

Have a read in

man bash
/^INVOCATION

Cheers,
Tink

amfoster · 10-28-2004, 05:14 PM

bash reads .bash_profile and .bashec
ksh reads .profile and .kshrc (.kshrc is default)
csh reads .login and .cshrc

I like to simply create a .profile and a .login file with the following statement in each of them:

if [ -f ~/.bash_profile ]
then
. ~/.bash_profile
fi

that can also be done like this:

[ -f ~/.bash_profile ] && . ~/.bash_profile

That way no matter which shell I use, I will simply be reading whatever is in the .bash_profile

Of course you can come up with your own way as well.

Tinkster · 10-28-2004, 05:17 PM

Quote:

Originally posted by amfoster
bash reads .bash_profile and .bashec
ksh reads .profile and .kshrc (.kshrc is default)
csh reads .login and .cshrc

That's not only overly simplistic, that's just plain
wrong ... maybe you want to read
man bash
/^INVOCATION
too?

Cheers,
Tink