Re: [HACKERS] postmaster locking issues. - Mailing list pgsql-hackers

From Bruce Momjian
Subject Re: [HACKERS] postmaster locking issues.
Date
Msg-id 199810121348.JAA01524@candle.pha.pa.us
Whole thread Raw
In response to Re: [HACKERS] postmaster locking issues.  ("Thomas G. Lockhart" <lockhart@alumni.caltech.edu>)
Responses Re: [HACKERS] postmaster locking issues.  ("Marc G. Fournier" <scrappy@hub.org>)
List pgsql-hackers
> > >> 5.  The port lock will be kept in '/var/opt/pgsql/lock/'.
>
> As everyone has pointed out, we can't count on a specific convention for
> where the lock file should go. However, we can probably count on a
> convention to be followed on a particular OS. That would seem to be
> something to define in Makefile.port, which could then be overridden by
> a configure option or Makefile.custom entry.
>
> On my RedHat Linux systems, the appropriate place seems to be /var/lock
> or /var/lock/pgsql.

I have talked to Billy.  I see no real value to try chasing around
OS-specific lock file locations.  /tmp is fine, and if they don't have
sticky bits in /tmp, they have much larger problems than the location of
the lock file.

--
  Bruce Momjian                        |  http://www.op.net/~candle
  maillist@candle.pha.pa.us            |  (610) 853-3000
  +  If your life is a hard drive,     |  830 Blythe Avenue
  +  Christ can be your backup.        |  Drexel Hill, Pennsylvania 19026


pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: [HACKERS] Open 6.4 items
Next
From: Bruce Momjian
Date:
Subject: Re: [HACKERS] Minor problem with Solaris 2.7beta