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

Re: Sure enough, the lock file is gone

From: Jan Wieck <janwieck(at)Yahoo(dot)com>
To: "Ross J(dot) Reedstrom" <reedstrm(at)rice(dot)edu>
Cc: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, Peter Eisentraut <peter_e(at)gmx(dot)net>, PostgreSQL Development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Sure enough, the lock file is gone
Date: 2001-01-26 20:50:39
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers
Ross J. Reedstrom wrote:
> On Fri, Jan 26, 2001 at 03:18:13PM -0500, Bruce Momjian 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.
> >
> > If we have to do it, let's make it an #ifdef __linux__ option.
> ISTR mention of non-linux platforms that do this.

    Exactly  the way you want it to do (open(2) and close(2) of a
    UNIX domain socket) was what I  had  to  do  to  get  an  old
    Mach3-4.3BSD combo into a kernel-panic.

    Better use utime(2) or the like for it.



# It's easier to get forgiveness for being wrong than for being right. #
# Let's break this rule - forgive me.                                  #
#================================================== JanWieck(at)Yahoo(dot)com #

Do You Yahoo!?
Get your free address at

In response to


pgsql-hackers by date

Next:From: Bruce MomjianDate: 2001-01-26 20:57:17
Subject: Re: Open 7.1 items
Previous:From: Alfred PerlsteinDate: 2001-01-26 20:49:30
Subject: Re: Sure enough, the lock file is gone

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