Thanks Steven,
The setenv was used just to prove that the .bash_profile was being set -
which it did. The shell in use is bash.
Your explanation is quite thorough and I appreciate it Steven,
however, why is the .bash_profile definition not preserved?
Steven W. Orr wrote:
On Wednesday, Aug 16th 2006 at 14:08 +0100, quoth Martin Raskovsky:
=>Hi,
=>
=>I have just installed Red Hat Enterpresie 4 and have a problem with
=>LD_LIBRARY_PATH which is set in my .bash_profile but appears unset in all
=>shells. I have even placed a setenv > log as the last statement in the
=>.bash_profile, the file does contain the correct LD_LIBRARY_PATH definition.
=>
=>Needless to say, there is an export statement for LD_LIBRARY_PATH.
=>All other environment definitions including PATH are correctly preserved.
=>I am using GNOME
The LD_LIBRARY_PATH variable should hardly *ever* be set. Please use the
/etc/ld.so.conf file instead. The only time you should be using this
variable is if you are running a program which has a choice at execution
time for which shared library you want to select from.
Having said all that, the setenv is a csh command and you seem to be
setting your variable in your .bash_profile
Wrong place dude. If you are running a csh flavored shell then you need to
set it in you ~/.login
_______________________________________________
Redhat-devel-list mailing list
Redhat-devel-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/redhat-devel-list
_______________________________________________
Redhat-devel-list mailing list
Redhat-devel-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/redhat-devel-list
