Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm 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 Message-ID: <41BC4DA5.9000800@familiehaase.de> Date: Sun, 12 Dec 2004 14:54:45 +0100 From: "Gerrit P. Haase" Organization: Esse keine toten Tiere User-Agent: Mozilla/5.0 (Windows; U; WinNT4.0; de-AT; rv:1.7.3) Gecko/20040910 MIME-Version: 1.0 To: cygwin AT cygwin DOT com Subject: Re: [Fwd: [gp AT familiehaase DOT de: sem_* functions in cygwin]] References: <20041209164442 DOT GA25246 AT cygbert DOT vinschen DOT de> In-Reply-To: <20041209164442.GA25246@cygbert.vinschen.de> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Corinna Vinschen wrote: > [Catching up on some older mails] > > >>----- Forwarded message from "Gerrit P. Haase" ----- >>From: "Gerrit P. Haase" >>To: cygwin ML >>Subject: sem_* functions in cygwin >>Date: Sun, 21 Nov 2004 22:48:20 +0100 >> >>Hi, >> >>nearly all sem_* functions are available, but sem_unlock is missing, >>was there a problem implementing sem_unlock() or was it just missed >>by accident? >> >> >>Gerrit >>----- End forwarded message ----- > > > I guess you're asking about sem_unlink(). It's not implemented so far > since named POSIX semaphores are implemented using named Windows semaphores. > The SUSv3 description contains a pretty unfortunate implementation detail: > > Calls to sem_open() to recreate or reconnect to the semaphore refer > to a new semaphore after sem_unlink() is called. > > There's no way I know of, which allows to implement this using named > Windows semaphores. At least not without adding a lot of annoying > bookkeeping overhead, possibly involving cygserver. I got an undefined reference to sem_unlock(). Gerrit -- =^..^= -- 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/