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

Re: Sure enough, the lock file is gone

From: "Oliver Elphick" <olly(at)lfix(dot)co(dot)uk>
To: Jan Wieck <janwieck(at)Yahoo(dot)com>
Cc: Peter Eisentraut <peter_e(at)gmx(dot)net>, "Ross J(dot) Reedstrom" <reedstrm(at)rice(dot)edu>, Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, PostgreSQL Development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Sure enough, the lock file is gone
Date: 2001-01-27 12:29:28
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers
Jan Wieck wrote:
  >Peter Eisentraut wrote:
  >> Jan Wieck writes:
  >> >     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.
  >> The lock file is an ordinary file.
  >    So  the  crazy-temp-vacuum-cleaner on linux doesn't touch the
  >    sockets?
tmpreaper does - that's why I moved the socket in Debian.

Oliver Elphick                                Oliver(dot)Elphick(at)lfix(dot)co(dot)uk
Isle of Wight                    
PGP: 1024R/32B8FAA1: 97 EA 1D 47 72 3F 28 47  6B 7E 39 CC 56 E4 C1 47
GPG: 1024D/3E1D0C1C: CA12 09E0 E8D5 8870 5839  932A 614D 4C34 3E1D 0C1C
     "Come now, and let us reason together, saith the LORD; 
      though your sins be as scarlet, they shall be as white
      as snow; though they be red like crimson, they shall 
      be as wool."                     Isaiah 1:18 


pgsql-hackers by date

Next:From: Philip WarnerDate: 2001-01-27 12:37:30
Subject: Re: pg_dump -c database problem
Previous:From: GB Clark IIDate: 2001-01-27 11:07:49
Subject: Re: Sure enough, the lock file is gone

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