Re: Sure enough, the lock file is gone

From: Alfred Perlstein <bright(at)wintelcom(dot)net>
To: Peter Eisentraut <peter_e(at)gmx(dot)net>
Cc: PostgreSQL Development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Sure enough, the lock file is gone
Date: 2001-01-26 20:49:30
Message-ID: 20010126124929.H26076@fw.wintelcom.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

* Peter Eisentraut <peter_e(at)gmx(dot)net> [010126 12:11] wrote:
> The 'tmpwatch' program on Red Hat will remove the /tmp/.s.PGSQL.5432.lock
> file after the server has run 6 days. This will be a problem.
>
> We could touch (open) the file once every time the ServerLoop() runs
> around. It's not perfect but it should work in practice.

Why not have the RPM/configure scripts stick it in where ever redhat
says it's safe to?

--
-Alfred Perlstein - [bright(at)wintelcom(dot)net|alfred(at)freebsd(dot)org]
"I have the heart of a child; I keep it in a jar on my desk."

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Jan Wieck 2001-01-26 20:50:39 Re: Sure enough, the lock file is gone
Previous Message Bruce Momjian 2001-01-26 20:35:22 Re: This script will crash the connection