From: | Tomas Berndtsson <tomas(at)nocrew(dot)org> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Randall Perry <rgp(at)systame(dot)com>, pgsql-general(at)postgresql(dot)org |
Subject: | Re: Serious environment problem with 7.2 on Solaris |
Date: | 2002-05-13 14:45:43 |
Message-ID: | 80it5sumw8.fsf@junk.nocrew.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> writes:
> Randall Perry <rgp(at)systame(dot)com> writes:
> > 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.
>
> Hm. Not sure about Solaris, but on HPUX plain "su postgres" does not
> run postgres' login script. You have to do "su - postgres" to make that
> happen. Perhaps Solaris has some similar distinction?
Solaris is paranoid. It will only read the profile files for 'su -
user' if the shell for the user is '/usr/bin/sh'. Nothing else is
allowed, or the profile file is not read.
At least this is true for Solaris 8, not sure about others.
Tomas
From | Date | Subject | |
---|---|---|---|
Next Message | Jérôme Tollet | 2002-05-13 14:53:34 | INT UNSIGNED problem |
Previous Message | Thomas Lockhart | 2002-05-13 14:42:35 | Re: Why is ALLOW_ABSOLUTE_DBPATHS unsafe? |