X-Recipient:	archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status:	No, hits=-2.4 required=5.0 tests=AWL,BAYES_00,KHOP_THREADED,RP_MATCHES_RCVD,SPF_HELO_PASS
X-Spam-Check-By:	sourceware.org
Message-ID:	<5064136F.5090609@malth.us>
Date:	Thu, 27 Sep 2012 01:50:55 -0700
From:	"Gregory M. Turner" <gmt AT malth DOT us>
User-Agent:	Mozilla/5.0 (Windows NT 6.1; WOW64; rv:15.0) Gecko/20120907 Thunderbird/15.0.1
MIME-Version:	1.0
To:	cygwin AT cygwin DOT com
CC:	mgsexton1 AT gmail DOT com
Subject:	Re: No support for sharing unnamed semaphores between processes through shared memory?
References:	<CALom-kwFp1EAfb4g5fqB6xrPR8Cak+3jSrr289mgao1B9U7HOw AT mail DOT gmail DOT com> <50621C0F DOT 7050208 AT tlinx DOT org>
In-Reply-To:	<50621C0F.7050208@tlinx.org>
X-IsSubscribed:	yes
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/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

On 9/25/2012 2:03 PM, Linda Walsh wrote:
> Matt Sexton wrote:
>> Hello,
>>
>> I am attempting to port to Cygwin an application that synchronizes
>> between processes using unnamed semaphores in shared memory.  Both
>> processes have mapped the shared memory region, one process
>> initialize
> ----
>      There's a cygwin process that you have to have running
> for shared memory that "hosts" or holds on to the shared
> memory.
>
> I think it is the Cygwin cygserver....(but don't kill me if I'm wrong)...
>
> Something needs to hang around and hold onto that shared memory, or windows
> will recycle it.

It is cygserver -- in my limited experience, the shm works as advertised.

See http://cygwin.com/cygwin-ug-net/using-cygserver.html for gory 
details (actually, not so gory at all).

Remember to shut it down when running setup.exe, or if you rebase (this, 
because it's a regular cygwin process -- for the same reason, if you 
manage to wedge cygwin's pseudo-kernel, you may need to bounce the 
service, in addition to killing off all your other cygwin processes, 
before cygwin will so-to-speak "reboot" and unwedge).

-gmt


--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

- Raw text -