Re: Serious environment problem with 7.2 on Solaris

I tried running this command in my CRON job just before the script command:
setenv LD_LIBRARY_PATH
"/usr/local/lib:/usr/local/ssl/lib:/usr/local/lib/sasl"

And got the error:

sh: setenv: not found

What shell does CRON use?

> Sorry, I didn't really think about my previous reply, here are some more
> thoughts.
> We have had real problems setting the LD_LIBRARY_PATH and LD_RUN_PATH
> variables as well. These need to be set in every environment (Perl DBI,
> crontab, profile etc.) that calls ld.
>
>
> USERS
> $ su
> Doesn't execute $HOME/.profile
> Remote users, or those that login will execute the .profile
>
> SO FOR CRONTAB
> 1. Set the variables in the crontab file as environment variables (I am told
> you can do this at the start of the crontab file?, but I haven't tried it
> yet).
> 2. Set the environment variable in the shell that includes postgresql
> commands.
>
>
> LD_RUN_PATH - I've had to set this at compile time when compiling Solaris 8
> x86
>
> Hope this helps,
>
> David.
>
>
>
> -----Original Message-----
> From: Randall Perry [mailto:rgp(at)systame(dot)com]
> Sent: 11 May 2002 20:01
> To: pgsql-general(at)postgresql(dot)org
> Subject: [GENERAL] Serious environment problem with 7.2 on Solaris
>
>
> Having major trouble with LD_LIBRARY_PATH env variable under 7.2. Getting
> the error:
>
> ld.so.1: psql: fatal: libgcc_s.so.1: open failed: No such file or directory
> Killed
>
> When starting.
>
> LD_LIBRARY_PATH is set in root & postgres login script, but strange things
> are happening with it. If I ssh into server using postgres account
> LD_LIBRARY_PATH is set. But if I su postgres from another account it isn't,
> though all other variables from login script are set ok.
>
> If I switch back to 7.1.3, no problem. Below are the situations where I can
> and cannot connect.
>
> Is there some PgSQL misconfiguration I'm missing, or could there have been
> something wrong with the compile?
>
>
>
> 7.1.3:
> no env problems
>
> 7.2:
> root can connect
> root cron jobs can't connect, libgcc_s.so.1: open failed
> remote users can connect
> sudo root can't connect, libgcc_s.so.1: open failed
> su postgres can't connect, libgcc_s.so.1: open failed
> ssh postgres can connect
>

--
Randy Perry
sysTame
Mac Consulting/Sales

phn 772.589.6449
mobile email help(at)systame(dot)com