From: | The Hermit Hacker <scrappy(at)hub(dot)org> |
---|---|
To: | Lamar Owen <lamar(dot)owen(at)wgcr(dot)org> |
Cc: | Florent Guillaume <efgeor(at)noos(dot)fr>, <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Re: Sure enough, the lock file is gone |
Date: | 2001-01-27 19:14:13 |
Message-ID: | Pine.BSF.4.31.0101271512480.577-100000@thelab.hub.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | 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(at)hub(dot)org secondary: scrappy(at){freebsd|postgresql}.org
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2001-01-27 19:24:17 | Re: new version of contrib-intarray |
Previous Message | Lamar Owen | 2001-01-27 19:09:11 | Re: Re: Sure enough, the lock file is gone |