Re: Re: problems with startup script on upgrade

From: Alexander Klimov <ask(at)wisdom(dot)weizmann(dot)ac(dot)il>
To: Peter Eisentraut <peter_e(at)gmx(dot)net>
Cc: "Martin A(dot) Marques" <martin(at)math(dot)unl(dot)edu(dot)ar>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Re: problems with startup script on upgrade
Date: 2001-03-19 11:47:37
Message-ID: Pine.SUN.4.21.0103191033420.1673-100000@dardar.wisdom.weizmann.ac.il
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Sun, 18 Mar 2001, Peter Eisentraut wrote:
> Alexander Klimov writes:
> > There are many way to solve the problem:
> > the easy -- copy (or link) libz.so to /usr/lib
> > the clean -- avoid using LD_LIBRARY_PATH, use -R for linking instead
>
> Our makefiles are set up to use '-R' for linking. Does this not work as
> designed?

It depends on what it was designed for :-) My guess is that currently
there is only something like `-R/usr/local/pgsql' in linking, but not for
locations of other libraries: libz, libssl, libcrypto, etc.

I guess that Martin's case of running postgress as `secure application' is
something unusual, but there is more usual case: if you run apache as root
(to be able to bind it to port 80) and then use from perl libpq (compiled
with ssl) you will definitely have a trouble -- ssl will not be found.

Regards,
ASK

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Zeugswetter Andreas SB 2001-03-19 12:15:52 AW: AW: Re[4]: Allowing WAL fsync to be done via O_SYNC
Previous Message Peter Galbavy 2001-03-19 11:00:20 FAQ: Current state of replication ?