Re: Re: Sure enough, the lock file is gone - Mailing list pgsql-hackers

From The Hermit Hacker
Subject Re: Re: Sure enough, the lock file is gone
Date
Msg-id Pine.BSF.4.31.0101271512480.577-100000@thelab.hub.org
Whole thread Raw
In response to Re: Re: Sure enough, the lock file is gone  (Lamar Owen <lamar.owen@wgcr.org>)
List pgsql-hackers
first off, the lock file is put in by an unprivileged user, so /tmp works
on all systems ...

second, /tmp on a large portion of systems gets cleaned out after a
reboot, so there are no 'stray locks' to generally worry about...


On Sat, 27 Jan 2001, Lamar Owen wrote:

> Florent Guillaume wrote:
> >
> > /tmp is for *temporary* files. Such a lock is not a temporary file, it
> > should go somewhere in /var, why not in /var/lib/pgsql/data ?
>
> /var/lib is also not for locks, per FHS.
>
> /var/lock/pgsql (or /var/lock/postgresql....) would be the FHS-mandated
> place for such a file.
>
> Comments?  _Why_ is the lock in /tmp?  Won't the lock always be put into
> place by the uid used to run postmaster?  Is a _world_ writeable
> temporary directory the right place?
>
> 7.2 discussion, however, IMHO.
> --
> Lamar Owen
> WGCR Internet Radio
> 1 Peter 4:11
>

Marc G. Fournier                   ICQ#7615664               IRC Nick: Scrappy
Systems Administrator @ hub.org
primary: scrappy@hub.org           secondary: scrappy@{freebsd|postgresql}.org



pgsql-hackers by date:

Previous
From: Lamar Owen
Date:
Subject: Re: Re: Sure enough, the lock file is gone
Next
From: Tom Lane
Date:
Subject: Re: new version of contrib-intarray