Postgres Pro
Downloads
Home   >   mailing lists

Thread: Re: [HACKERS] postmaster crash and .s.pgsql file

Re: [HACKERS] postmaster crash and .s.pgsql file

From
Andrew Martin
Date:
>    > I would opt for /var/run to store the pid files and have the name set to
>
>        That would assume that postmaster runs as root, which is not
>    allowed...has to be in /tmp somewhere
>
> Maybe both should be under /usr/local/pgsql
I assume you mean the root of the installation rather than specifically
/usr/local/pgsql.

> somewhere, so they will not be removed by any
> '/tmp'-clean-up-scripts.
>
In $PGDATA would seem as good as anywhere (maybe $PGDATA/.run or some such)

/usr/local is mounted r/o on my system - $PGDATA lives elsewhere and is
writable.

Andrew
----------------------------------------------------------------------------
Dr. Andrew C.R. Martin                             University College London
EMAIL: (Work) martin@biochem.ucl.ac.uk    (Home) andrew@stagleys.demon.co.uk
URL:   http://www.biochem.ucl.ac.uk/~martin
Tel:   (Work) +44(0)171 419 3890                    (Home) +44(0)1372 275775

Re: [HACKERS] postmaster crash and .s.pgsql file

From
The Hermit Hacker
Date:
On Thu, 29 Jan 1998, Andrew Martin wrote:

> >    > I would opt for /var/run to store the pid files and have the name set to
> >
> >        That would assume that postmaster runs as root, which is not
> >    allowed...has to be in /tmp somewhere
> >
> > Maybe both should be under /usr/local/pgsql
> I assume you mean the root of the installation rather than specifically
> /usr/local/pgsql.
>
> > somewhere, so they will not be removed by any
> > '/tmp'-clean-up-scripts.
> >
> In $PGDATA would seem as good as anywhere (maybe $PGDATA/.run or some such)
>
> /usr/local is mounted r/o on my system - $PGDATA lives elsewhere and is
> writable.

    $PGDATA is created 700...general users need to be able to read the
directory in order to connect to the socket, so we'd have to lax up
security in order to accomplish this...

Re: [HACKERS] postmaster crash and .s.pgsql file

From
Goran Thyni
Date:
   > > somewhere, so they will not be removed by any
   > > '/tmp'-clean-up-scripts.

I am convinced.
We better leave the socket in /tmp .
Any tmpwatch-scripts should not touch dot-files anyway.

<EXPLAIN>
A tmpwatch-script runs under cron and cleans out old file
from /tmp.
tmpwatch command (at least under RH5-Linux) does not touch
special-files unless -a is specified.
</EXPLAIN>

    terveiset,
--
---------------------------------------------
G�ran Thyni, sysadm, JMS Bildbasen, Kiruna