From: "Gregory M. Turner" <gmt@malth.us>
To: cygwin@cygwin.com
Cc: mgsexton1@gmail.com
Subject: Re: No support for sharing unnamed semaphores between processes through shared memory?
Date: Thu, 27 Sep 2012 10:26:00 -0000 [thread overview]
Message-ID: <5064136F.5090609@malth.us> (raw)
In-Reply-To: <50621C0F.7050208@tlinx.org>
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
next prev parent reply other threads:[~2012-09-27 8:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-10 19:17 Matt Sexton
2012-09-25 21:20 ` Linda Walsh
2012-09-27 10:26 ` Gregory M. Turner [this message]
2012-10-09 13:54 ` Corinna Vinschen
2012-10-09 13:54 ` Corinna Vinschen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5064136F.5090609@malth.us \
--to=gmt@malth.us \
--cc=cygwin@cygwin.com \
--cc=mgsexton1@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).