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

Re: Re: Sure enough, the lock file is gone

From: Lamar Owen <lamar(dot)owen(at)wgcr(dot)org>
To: Peter Eisentraut <peter_e(at)gmx(dot)net>
Cc: The Hermit Hacker <scrappy(at)hub(dot)org>, Florent Guillaume <efgeor(at)noos(dot)fr>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Re: Sure enough, the lock file is gone
Date: 2001-01-27 19:56:36
Message-ID: 3A7327F4.D6411F88@wgcr.org (view raw or flat)
Thread:
Lists: pgsql-hackers
Peter Eisentraut wrote:
> Lamar Owen writes:
> > I understand why the socket needs to be in /tmp, but why the lockfile?
 
> The lock file protects the Unix domain socket.  Consequently, the name of
> the lock file needs to be derivable from the name of the socket file, and
> vice versa.  Also, the name of the socket file must not vary with other
> parameters such as installation layout.

I see.
--
Lamar Owen
WGCR Internet Radio
1 Peter 4:11

In response to

Responses

pgsql-hackers by date

Next:From: Peter EisentrautDate: 2001-01-27 19:58:59
Subject: Re: Re: Sure enough, the lock file is gone
Previous:From: Lamar OwenDate: 2001-01-27 19:28:32
Subject: Re: Re: Sure enough, the lock file is gone

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