Re: location of the configuration files

<br /><br /> Robert Treat wrote:<br /><blockquote cite="mid1045176269.12930.576.camel@camel" type="cite"><pre
wrap="">OnThu, 2003-02-13 at 14:51, mlw wrote: </pre><blockquote type="cite"><pre wrap="">
 
Robert Treat wrote:


On Thu, 2003-02-13 at 12:13, mlw wrote:
 

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'


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.


postmaster.opts, PG_VERSION, and postmaster.pid are not configuration
parameters. 
   </pre></blockquote><pre wrap="">
So? I'm not saying they all have to be moved, just they all need to be
accounted for. </pre></blockquote> OK, what was the point?<br /><br /><blockquote
cite="mid1045176269.12930.576.camel@camel"type="cite"><blockquote type="cite"><pre wrap="">PG_VERSION is VERY
important,it is how you know the version of the
 
database.
Postmaster.pid is a postgres writable value 
AFAIK, postmaster.opts is also a postgres writable value.
   </pre></blockquote><pre wrap="">
IIRC the postmaster.pid file should be in /var/run according to FHS, I'm
not sure about postmaster.opts though...

Again, if we're going to make a change, let's make sure we think it
through.</pre></blockquote> I'm not a big fan of the "/var/run" directory convention, especially when we expect
multipleinstances of the server to be able to run concurrently. I suppose it can be a parameter in both the
configurationfile and command line.<br /><br />