Re: Sure enough, the lock file is gone - Mailing list pgsql-hackers

From Jan Wieck
Subject Re: Sure enough, the lock file is gone
Date
Msg-id 200101262050.PAA04327@jupiter.greatbridge.com
Whole thread Raw
In response to Re: Sure enough, the lock file is gone  ("Ross J. Reedstrom" <reedstrm@rice.edu>)
Responses Re: Sure enough, the lock file is gone  (Peter Eisentraut <peter_e@gmx.net>)
List 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.
>
> #ifdef BRAINDAMAGED_TMP_CLEANER ?
>
> 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.


Jan

--

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



_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com



pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: This script will crash the connection
Next
From: Peter Eisentraut
Date:
Subject: Re: beta3 Solaris 7 (SPARC) port report