| From: | "Marc G(dot) Fournier" <scrappy(at)hub(dot)org> |
|---|---|
| To: | "Thomas G(dot) Lockhart" <lockhart(at)alumni(dot)caltech(dot)edu> |
| Cc: | "Billy G(dot) Allie" <Bill(dot)Allie(at)mug(dot)org>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Taral <taral(at)mail(dot)utexas(dot)edu>, hackers(at)postgreSQL(dot)org |
| Subject: | Re: [HACKERS] postmaster locking issues. |
| Date: | 1998-10-15 09:56:50 |
| Message-ID: | Pine.BSF.4.05.9810150554200.4514-100000@hub.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, 12 Oct 1998, Thomas G. Lockhart wrote:
> > >> 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.
FreeBSD has a /var/spool/lock...Solaris has /var/spool/locks
Hrmmmm...there are a couple of ways of doing this...we could put
it into the template for the OS as a -DLOCK_DIR="", which would probably
be the simplist (instead of having configure searching all
possibilities)...
Marc G. Fournier scrappy(at)hub(dot)org
Systems Administrator @ hub.org
scrappy(at){postgresql|isc}.org ICQ#7615664
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Marc G. Fournier | 1998-10-15 09:59:35 | Re: [HACKERS] postmaster locking issues. |
| Previous Message | Andreas Zeugswetter | 1998-10-15 08:56:50 | Re: order by and index path |