"Martin A. Marques" <[EMAIL PROTECTED]> writes:
> Now, libz.so is in the LD_LIBRARY_PATH of the postgres user, so why is it
> that Solaris doesn't load the .profile in the postgres directory.
Ah, but is the LD_LIBRARY_PATH the same inside that su? A change of
environment might explain why this
"Martin A. Marques" <[EMAIL PROTECTED]> writes:
>> Hm, that 'Killed' looks suspicious. What shows up in the
>> /dbs/postgres/sql.log file?
> Nothing at all.
That's no help :-(. Please alter the command to trace the shell script,
ie
su postgres -c 'sh -x /dbs/postgres/bin/pg_ctl -o ... 2>trace
"Martin A. Marques" <[EMAIL PROTECTED]> writes:
>> Please define "doesn't work". What happens exactly? What messages
>> are produced?
> root@ultra31 /space/pruebas/postgres-cvs # su postgres -c
> '/dbs/postgres/bin/pg_ctl -o "-i" -D /dbs/postgres/data/ start -l
> /dbs/postgres/sql.log'
> 1905
"Martin A. Marques" <[EMAIL PROTECTED]> writes:
> ... my startup scripts don't work anymore.
> What the script has, works if I try to do it as postgres, but with a
> su -l postgres -c 'command' as root it doesn't work.
Please define "doesn't work". What happens exactly? What messages
are produ
