X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=0.7 required=5.0 tests=AWL,BAYES_00,SARE_MSGID_LONG40,SPF_PASS X-Spam-Check-By: sourceware.org MIME-Version: 1.0 In-Reply-To: <20090612191212.GH5039@calimero.vinschen.de> References: <94b5b62d0906112150g473b49fao41f95c3a1c6e6014 AT mail DOT gmail DOT com> <20090612084932 DOT GC5039 AT calimero DOT vinschen DOT de> <94b5b62d0906121156m197fc1f4j3c83c3796c741de4 AT mail DOT gmail DOT com> <20090612191212 DOT GH5039 AT calimero DOT vinschen DOT de> Date: Fri, 12 Jun 2009 23:20:10 -0300 Message-ID: <94b5b62d0906121920w6f9b0c87l83aeba3271f13bae@mail.gmail.com> Subject: Re: 1.7.0 sem_open From: Pedro Izecksohn To: cygwin AT cygwin DOT com Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com >> =C2=A0 The persistence of the semaphore also works for you? >> >> =C2=A0 For me, using the unpatched version, (not the CVS version), the >> persistence works some times only. At other times the semaphore >> disappears with the Control c. > > The semaphore is backed by a file on disk. =C2=A0If you don't call > sem_unlink one way or the other, the semaphore persists. Nice to say, but why it is not always this way? I should create an example to run my code some times and always kill it until that the semaphore does not persist. It is a nice task for tonight. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/