From: | Randall Perry <rgp(at)systame(dot)com> |
---|---|
To: | <pgsql-general(at)postgresql(dot)org> |
Cc: | <david(dot)morgan(at)s4c(dot)co(dot)uk> |
Subject: | Re: Serious environment problem with 7.2 on Solaris |
Date: | 2002-05-13 17:31:34 |
Message-ID: | B90570B6.14A97%rgp@systame.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
I'll answer my own question; bash syntax works:
LD_LIBRARY_PATH=/usr/local/lib:/usr/local/ssl/lib:/usr/local/lib/sasl;
export LD_LIBRARY_PATH; <script command>
I'll have to precede each script that uses PgSQL with this to get it to work
with CRON (Unless someone knows a way to set env for all CRON jobs).
Now the next problem: setting the env for my CGI scripts! :(
> 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?
--
Randy Perry
sysTame
Mac Consulting/Sales
phn 772.589.6449
mobile email help(at)systame(dot)com
From | Date | Subject | |
---|---|---|---|
Next Message | Steve Lane | 2002-05-13 17:47:01 | Re: Can This be done |
Previous Message | Scott Marlowe | 2002-05-13 17:24:48 | Re: if exists? |