<br /><br /> Bruce Momjian wrote:<br /><blockquote cite="mid200302131943.h1DJhS211683@candle.pha.pa.us"
type="cite"><prewrap="">Robert Treat wrote: </pre><blockquote type="cite"><pre wrap="">On Thu, 2003-02-13 at 12:13, mlw
wrote: </pre><blockquote type="cite"><pre wrap="">My patch only works on the PostgreSQL server code. No changes have
been
made to the initialization scripts.
The patch declares three extra configuration file parameters:
hbafile= '/etc/postgres/pg_hba.conf'
identfile='/etc/postgres/pg_ident.conf'
datadir='/RAID0/postgres'
</pre></blockquote><pre wrap="">If we're going to do this, I think we need to account for all of the
files in the directory including PG_VERSION, postmaster.opts,
postmaster.pid. In the end if we can't build so that we are either fully
FHS compliant and/or LSB compliant, we've not done enough work on it. </pre></blockquote><pre wrap="">
Woh, how do we move some of those files into /etc or /var/run if we
aren't running as root? We certainly don't want to require that. I
guess /etc/postgresql will work if that directory is owned by the
PostgreSQL superuser, but /var/run will be a problem.
</pre></blockquote> I don't think those files need to move. As I said in another post, they are postgres writable and
shouldin the PostgreSQL data directory. However, I suppose, that those also could be configuration parameters? No?<br
/><br/> PG_VERSION obviously should not move.<br /> postmaster.opts gets created when postmaster is run, correct?<br
/><br/> The only issue would be the PID file, and I don't have strong feelings about it, except that using a /var/run
systemwill make running multiple postmasters a pain.<br /><br /><br />
