Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe@cygwin.com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin@cygwin.com>
List-Help: <mailto:cygwin-help@cygwin.com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Delivered-To: mailing list cygwin@cygwin.com
X-Authentication-Warning: atacama.four-d.de: mail set sender to <tpfaff@gmx.net> using -f
Message-ID: <3E34E7D6.8010306@gmx.net>
Date: Mon, 27 Jan 2003 09:03:34 +0100
From: Thomas Pfaff <tpfaff@gmx.net>
User-Agent: Mozilla/5.0 (Windows; U; WinNT4.0; en-US; rv:1.2.1) Gecko/20021130
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Elliot Mednick <elliot@cadence.com>
CC: cygwin@cygwin.com
Subject: Re: Mmap and semaphores?
References: <B64C24D6DF7BF040BAF59B923D06180B3FEFC8@exmbx01chel.cadence.com>
In-Reply-To: <B64C24D6DF7BF040BAF59B923D06180B3FEFC8@exmbx01chel.cadence.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

Please check the sem_init return code first.
Cygwin does not support process shared semaphores at the moment.

Thomas

Elliot Mednick wrote:
> Hello,
> 
> I'm try to write a client server application that used shared memory and
> asemaphores.  Appended is a simple test case.  It works under Solaris
> using the -lposix4 library.  But it doesn't work under Cygwin.  Given
> the lack of any otherquestions about this, I imagine that I'm doing
> something wrong, or it's functionality is limited.
> 
> The server maps a file as shared, inits a semaphore, then waits.  The
> client, which you start after the server waits, shares the same file
> (this part works) and attempts to post the semaphore.  The server ought
> to -- but doesn't -- wake up.  It does in Solaris.


--
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/

