Re: [HACKERS] flock patch breaks things here - Mailing list pgsql-hackers

From The Hermit Hacker
Subject Re: [HACKERS] flock patch breaks things here
Date
Msg-id Pine.BSF.4.02.9808301618350.343-100000@thelab.hub.org
Whole thread Raw
In response to Re: [HACKERS] flock patch breaks things here  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: [HACKERS] flock patch breaks things here  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Sun, 30 Aug 1998, Tom Lane wrote:

> Massimo Dal Zotto <dz@cs.unitn.it> writes:
> > In my opinion the socket and the pidfile should be created in a
> > directory owned by postgres, for example /tmp/.Pgsql-unix, like does X.
>
> The pidfile belongs at the top level of the database directory (eg,
> /usr/local/pgsql/data/postmaster.pid), because what it actually
> represents is that there is a postmaster running *for that database
> group*.

    I have to agree with this one...but then it also negates the
argument about the flock() DoS...*grin*

    BTW...I like the kill(pid,0) solution myself, primarily because it
is, i think, the most portable solution.

    I would not consider a patch to remove the flock() solution and
replace it with the kill(pid,0) solution a new feature, just an
improvement of an existing one...either way, moving the pid file (or
socket, for that matter) from /tmp should be listed as a security related
requirement for v6.4 :)

Marc G. Fournier
Systems Administrator @ hub.org
primary: scrappy@hub.org           secondary: scrappy@{freebsd|postgresql}.org


pgsql-hackers by date:

Previous
From: The Hermit Hacker
Date:
Subject: Re: [HACKERS] Release 6.4
Next
From: The Hermit Hacker
Date:
Subject: Re: [HACKERS] pgindent for Monday