Skip site navigation (1) Skip section navigation (2)

Re: [HACKERS] flock patch breaks things here

From: The Hermit Hacker <scrappy(at)hub(dot)org>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: PostgreSQL Hackers <hackers(at)postgreSQL(dot)org>
Subject: Re: [HACKERS] flock patch breaks things here
Date: 1998-10-30 02:11:02
Message-ID: Pine.BSF.4.05.9810292207190.28793-100000@thelab.hub.org (view raw or flat)
Thread:
Lists: pgsql-hackers
On Sun, 30 Aug 1998, Tom Lane wrote:

> The Hermit Hacker <scrappy(at)hub(dot)org> writes:
> > either way, moving the pid file (or
> > socket, for that matter) from /tmp should be listed as a security related
> > requirement for v6.4 :)
> 
> Huh?  There is no pid file being generated in /tmp (or anywhere else)
> at the moment.  If we do add one, it should not go into /tmp for the
> reasons I gave before.
> 
> Where the Unix-domain socket file lives is an entirely separate issue.
> 
> If we move the socket out of /tmp then we have just kicked away all the
> work we did to preserve backwards compatibility of the FE/BE protocol
> with existing clients.  Being able to talk to a 1.0 client isn't much
> good if you aren't listening where he's going to try to contact you.
> So I think I have to vote in favor of leaving the socket where it is.

Let me put my vote in...: $PGSQLHOME/run/{pgsql.pid,pgsql.pid.socket}

Screw backwards compatibility...v6.5 becomes v7.0 *shrug*

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


In response to

pgsql-hackers by date

Next:From: The Hermit HackerDate: 1998-10-30 02:14:04
Subject: Re: [HACKERS] Re: [COMMITTERS] 'pgsql/src/include/catalog pg_operator.h'
Previous:From: The Hermit HackerDate: 1998-10-30 02:06:25
Subject: Re: [HACKERS] Open 6.4 items

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group