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

From Lamar Owen
Subject Re: Re: Sure enough, the lock file is gone
Date
Msg-id 3A731CD7.6F0EA82B@wgcr.org
Whole thread Raw
In response to Re: Sure enough, the lock file is gone  (Florent Guillaume <efgeor@noos.fr>)
Responses Re: Re: Sure enough, the lock file is gone
List pgsql-hackers
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


pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: PgAccess - small bug?
Next
From: The Hermit Hacker
Date:
Subject: Re: Re: Sure enough, the lock file is gone