RE: Configurable path to look up dynamic libraries

I would like to bring my 2 grains of salt to the discussion.

The advantage of putting configuration files in etc is that the
administrator knows that all his configuration files are there. For backup
or upgrade purpose, it is easy to review the /etc directory and make
modifcation if needed. It is rather a pain to look everywhere where the
configuration files are...

PG could look first in datadir and if nothing is found then go in /etc. This
would allow to run multiple instance of postifix (conf in data dir) or one
instance with a a standard place to put the configuration file...

I would add also, that with the extension mechanism, it would be nice if PG
could look for .so in the standard library path.

Franck Martin
Network and Database Development Officer
SOPAC South Pacific Applied Geoscience Commission
Fiji
E-mail: franck(at)sopac(dot)org <mailto:franck(at)sopac(dot)org>
Web site: http://www.sopac.org/
<http://www.sopac.org/> Support FMaps: http://fmaps.sourceforge.net/
<http://fmaps.sourceforge.net/>

This e-mail is intended for its addresses only. Do not forward this e-mail
without approval. The views expressed in this e-mail may not be necessarily
the views of SOPAC.