This is the mail archive of the
mailing list for the Cygwin project.
Re: cygipc semaphores not persistent?
- From: Larry Hall <cygwin-lh at cygwin dot com>
- To: Mark Paulus <mark dot paulus at mci dot com>
- Cc: "cygwin at cygwin dot com" <cygwin at cygwin dot com>
- Date: Thu, 19 Jun 2003 14:55:47 -0400
- Subject: Re: cygipc semaphores not persistent?
- References: <0HGQ00JM8RU99X@pmismtp01.wcomnet.com>
- Reply-to: cygwin at cygwin dot com
No that's right. The goal was to move the functionality of cygipc into
the Cygwin DLL itself and expand on it. However, this work is incomplete.
But cygipc and the work to add IPC functionality to the Cygwin DLL are
mutually exclusive pieces of functionality. So there's nothing that's
happened that would affect the way that cygipc should function in the
Mark Paulus wrote:
Are you running the ipcdaemon process? At one time
the cygipc libraries required the ipcdaemon process
to manage the global objects. I thought I read something
that the ipc-daemon is going away, and being incorporated
into the cygwin architecture, but I did not gather that it had
happened yet. That may be a misunderstanding on my
On Thu, 19 Jun 2003 11:49:30 -0400, Joe Buehler wrote:
I am attempting to use cygipc for its semaphore functionality
in porting some existing UNIX code.
It would appear that semaphores are not persistent?
The code depends on the UNIX semantic of a semaphore being a global
system object that exists regardless of whether any processes are
currently using it.
I have processes coming and going, using the semaphore to mediate
access to a disk-based queue. I have been debugging the code,
and it appears that the semaphore is destroyed when no process has
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html