From: | Nathan Myers <ncm(at)zembu(dot)com> |
---|---|
To: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: location of Unix socket |
Date: | 2000-11-18 01:00:16 |
Message-ID: | 20001117170016.K12682@store.zembu.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Fri, Nov 17, 2000 at 04:49:43PM -0800, Alfred Perlstein wrote:
> * Oliver Elphick <olly(at)lfix(dot)co(dot)uk> [001117 16:41] wrote:
> > At present the Unix socket's location is hard-coded as /tmp.
> >
> > As a result of a bug report, I have moved it in the Debian package to
> > /var/run/postgresql/. (The bug was that tmpreaper was deleting it and
> > thus blocking new connections.)
> >
> > I suppose that we cannot assume that /var/run exists across all target
> > systems, so could the socket location be made a configurable parameter
> > in 7.1?
>
> What about X sockets and ssh-agent sockets, and so on?
> Where's the source to this thing? :)
>
> It would make more sense to fix tempreaper to ignore non regular
> files.
X sockets are in subdirectories, e.g. /tmp/.X11-unix/X0.
/tmp is a bad place for this stuff anyway.
Nathan Myers
ncm(at)zembu(dot)com
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2000-11-18 01:09:09 | Re: Varchar standard compliance |
Previous Message | Alfred Perlstein | 2000-11-18 00:49:43 | Re: location of Unix socket |