Re: Serious environment problem with 7.2 on Solaris

This may be a bad idea but you could try sourceing the /etc/profile
when running the script. This would theoretically give your environment
what was in the /etc/profile

May be a bad idea have never had to do it before

Just another 2 cents worth :-)

Darren Ferguson

On Mon, 13 May 2002, Randall Perry wrote:

> Ok, discovered that my 7.1.3 build does NOT require LD_LIBRARY_PATH -- but
> 7.2 does. This is why 7.1.3 wasn't a problem (it may have been built with
> the Sun compiler; I'm asking my ISP guy, who originally setup the server,
> about that -- I built 7.2 with gcc).
>
> And also discovered that sudo'ing, running CRON jobs, and running CGI
> scripts will not inherit user shell environemnts, so in these cases I have
> to find a way to export variables when using 7.2.
>
> I also tried setting DYNAMIC_LIBRARY_PATH var in postgresql.conf -- also
> didn't work.
>
> Is there any way to get env variables to appear in ALL environments, no
> matter what, under Solaris? I tried setting LD_LIBRARY_PATH in /etc/profile
> but that didn't work.
>
>
>
> > 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
>
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 2: you can get off all lists at once with the unregister command
> (send "unregister YourEmailAddressHere" to majordomo(at)postgresql(dot)org)
>