From: | teg(at)redhat(dot)com (Trond Eivind =?iso-8859-1?q?Glomsr=F8d?=) |
---|---|
To: | Lamar Owen <lamar(dot)owen(at)wgcr(dot)org> |
Cc: | Oliver Elphick <olly(at)lfix(dot)co(dot)uk>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Re: Sure enough, the lock file is gone |
Date: | 2001-01-28 23:37:39 |
Message-ID: | xuywvbfxn7g.fsf@halden.devel.redhat.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Lamar Owen <lamar(dot)owen(at)wgcr(dot)org> writes:
> 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.
FHS is a good starting (and end-) point.
--
Trond Eivind Glomsrød
Red Hat, Inc.
From | Date | Subject | |
---|---|---|---|
Next Message | Trond Eivind =?iso-8859-1?q?Glomsr=F8d?= | 2001-01-28 23:43:51 | Re: Re: Sure enough, the lock file is gone |
Previous Message | Lamar Owen | 2001-01-28 23:28:44 | Re: Re: Sure enough, the lock file is gone |