Make sure, if you're running .profile manually, that you run it as
". .profile". ("source .profile" in csh*)
If you execute a shellscript from the prompt, any environment variables it
sets, even if it exports them, will only be applicable to subshells
started "under" that script. If you source it into the shell environment
(. for bash, sh, etc, "source" for csh), you're telling the _shell_ to
maintain these variables, and they will be available to you in the shell
and in any programs you execute from that shell.
On Fri, 6 Apr 2001, Curt Russell Crandall wrote:
> Well, perhaps since most of the accounts already have LD_LIBRARY_PATH set,
> the ENV assignment is being overridden. I'm new to this set up
> here... it's an odd setup since my .profile seems to have no effect on my
> environment even if I execute .profile explicitly. I've just been setting
> LD_LIBRARY_PATH since that was how I was directed to connect t Sybase in
> my DBI scripts by the client. I don't recall ever setting something like
> this when working with Informix/AIX.
