Mailing-List: contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-developers-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin-developers AT sources DOT redhat DOT com Message-ID: <007a01c0c8ac$abc66550$0200a8c0@lifelesswks> From: "Robert Collins" To: Subject: gluttton for punishment Date: Thu, 19 Apr 2001 18:42:28 +1000 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 X-OriginalArrivalTime: 19 Apr 2001 08:34:59.0567 (UTC) FILETIME=[9ECE7FF0:01C0C8AB] That's me. I admit it. To test case the pshared mutex's I recently got going (getting cond vars working before I submit a patch - I am trying to avoid a tangled ball of spaghetti. I may fail at that :]) I wrote a bared bones SUS shmget, shmat ftok implementation for cygwin. How much interest is there in seeing that fleshed out and submitted? Also are shared memory id's meant to be cross-process persistent? I.E. if process A calls shmget(), possibly attachs and sets some data, and then exits (before another process calls shmget for the same memory area, does the shared memory area stay valid? If so, then I think egor's cygwin-server is a must - without that, when process A terminates, even if cygwin1.dll is still in memory, the shared memory mapping will be closed, and the data lost. Egor - how flexible is the server you have written? Chris - if the AT&T UWIN product supports shmget() then that's probably why they have a daemon component :] Rob