Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , 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: From: Tony_Chao AT putnam DOT com Date: Mon, 16 Sep 2002 11:42:23 -0400 MIME-Version: 1.0 Content-type: text/plain; charset=us-ascii 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/