| From: | Lamar Owen <lamar(dot)owen(at)wgcr(dot)org> |
|---|---|
| To: | Oliver Elphick <olly(at)lfix(dot)co(dot)uk> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Re: Sure enough, the lock file is gone |
| Date: | 2001-01-28 23:19:15 |
| Message-ID: | 3A74A8F3.987EEA25@wgcr.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Oliver Elphick wrote:
> No, UNIX sockets are specifically mentioned as belonging under /var/run.
> In section 5.10 "/var/run : Run-time variable data", it says: "Programs
> that maintain transient UNIX-domain sockets should place them in this
> directory."
>
> So what ever the outcome for the wider PostgreSQL community, I must make
> the change to conform to Debian policy.
So, if PostgreSQL is a part of Debian, then there will be problems if
the client-server situation isn't somehow fixed to allow robust
location-independent socket finding.
Looks like the same thing is going to happen with RedHat's
distribution. So, if this is going to occur, let's get a consensus as
to where that alternate location (barring some other solution) is going
to be, so that there are the fewest variants out there.
--
Lamar Owen
WGCR Internet Radio
1 Peter 4:11
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Lamar Owen | 2001-01-28 23:28:44 | Re: Re: Sure enough, the lock file is gone |
| Previous Message | Lamar Owen | 2001-01-28 23:13:30 | Re: Re: Sure enough, the lock file is gone |