From: | The Hermit Hacker <scrappy(at)hub(dot)org> |
---|---|
To: | Bruce Momjian <maillist(at)candle(dot)pha(dot)pa(dot)us> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, hackers(at)postgreSQL(dot)org |
Subject: | Re: [HACKERS] flock patch breaks things here |
Date: | 1998-10-30 20:16:43 |
Message-ID: | Pine.BSF.4.05.9810301616220.1918-100000@thelab.hub.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Fri, 30 Oct 1998, Bruce Momjian wrote:
> > The Hermit Hacker <scrappy(at)hub(dot)org> writes:
> > > On Sun, 30 Aug 1998, Tom Lane wrote:
> > >> 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*
> >
> > Catching up on back email, Marc?
> >
> > I think the end consensus of that thread was that we should move the
> > socket file to someplace safer than /tmp (exactly where being a
> > configure-time choice), *and* optionally put a softlink to it in /tmp
> > for backwards compatibility with old clients. Use of the /tmp link
> > would be deprecated because of possible security risks, but it could
> > continue to work for as long as a particular installation needed to
> > keep that option enabled.
>
> Just a reminder that if you move it, all clients must know the new
> location, or somehow the location must be accessable by the clients.
Which is only relevant if using Unix-domain sockets...
Marc G. Fournier
Systems Administrator @ hub.org
primary: scrappy(at)hub(dot)org secondary: scrappy(at){freebsd|postgresql}.org
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 1998-10-30 21:38:14 | Re: [HACKERS] HPUX 10.01 build issues and solutions. |
Previous Message | mschout | 1998-10-30 20:01:35 | HPUX 10.01 build issues and solutions. |