Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
Subject:	v1.3.12-2 shmctl(IPC_STAT) / postgres question
To:	cygwin AT cygwin DOT com
Message-ID:	<OF76BD6BA3.F0F9F290-ON85256C36.005471C3@putnaminv.com>
From:	Tony_Chao AT putnam DOT com
Date:	Mon, 16 Sep 2002 11:42:23 -0400
MIME-Version:	1.0

Hi.

I have postmaster install as an NT service through cygrunsrv.
Usually it shuts startsup and shutsdown fine.

But it seems that when the machine crashes, the service fails to start
because
it was unable to properly shutdown.

I originally thought this was a postgres issue with stale postmaster.pid
file, but the postgres folks
told me that even with a stale pid file, postmaster should start up because
it will then
perform more checking to see whether the shared memory is indeed in use.

So..I was wondering is shmctl(IPC_STAT) on cygwin behaving differently than
a
standard unix system? In particular, what error code does cygwin return if
there's no
such shared memory ID? Do the shared memory blocks indeed go away even
after
a machine crash+reboot?

Thanks for any help you can offer.

-Tony



--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

- Raw text -