From: | The Hermit Hacker <scrappy(at)hub(dot)org> |
---|---|
To: | Bruce Momjian <maillist(at)candle(dot)pha(dot)pa(dot)us> |
Cc: | Goran Thyni <goran(at)bildbasen(dot)se>, hackers(at)postgreSQL(dot)org |
Subject: | Re: [HACKERS] postmaster crash and .s.pgsql file |
Date: | 1998-01-26 23:24:06 |
Message-ID: | Pine.BSF.3.96.980126192149.252q-100000@thelab.hub.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Mon, 26 Jan 1998, The Hermit Hacker wrote:
> On Mon, 26 Jan 1998, Bruce Momjian wrote:
>
> >
> > When the postmaster crashes, it leaves the /tmp/.s.pgsql file in /tmp.
> > Is there a way to auto-remove it after a postmaster crash?
>
> If we wrote the process id to the file, if the file existed, we
> could read the process id and do a 'kill(pid, 0)', it "determines if a
> specific process still exists"...
>
> I'll try and look at it tonight, along with syslog() logging
Oops...I screwed up *rofl* I wasn't thinking when I wrote
this...I was thining that /tmp/.s.PGSQL was a lock file...I forgot it was
a socket :( forget me thing about the kill :) I haven't got a clue how
to detect whether it is active or not :(
Marc G. Fournier
Systems Administrator @ hub.org
primary: scrappy(at)hub(dot)org secondary: scrappy(at){freebsd|postgresql}.org
From | Date | Subject | |
---|---|---|---|
Next Message | James Hughes | 1998-01-26 23:32:13 | Re: [HACKERS] postmaster crash and .s.pgsql file |
Previous Message | Otto Villarin | 1998-01-26 23:11:54 |