X-Recipient: archive-cygwin AT delorie DOT com
X-Spam-Check-By: sourceware.org
Date: Fri, 12 Jun 2009 12:21:44 +0200
From: Corinna Vinschen <corinna-cygwin AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: 1.7.0 sem_open
Message-ID: <20090612102144.GC11934@calimero.vinschen.de>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <94b5b62d0906112150g473b49fao41f95c3a1c6e6014 AT mail DOT gmail DOT com> <20090612084932 DOT GC5039 AT calimero DOT vinschen DOT de>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20090612084932.GC5039@calimero.vinschen.de>
User-Agent: Mutt/1.5.19 (2009-02-20)
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
List-Id: <cygwin.cygwin.com>
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT 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 Jun 12 10:49, Corinna Vinschen wrote:
> SUSv4 states:
> 
>   The name argument conforms to the construction rules for a pathname,
>   except that the interpretation of <slash> characters other than the
>   leading <slash> character in name is implementation-defined, [...]
> 
>   If name begins with the <slash> character, then processes calling
>   sem_open() with the same value of name shall refer to the same semaphore
>   object, as long as that name has not been removed. If name does not
>   begin with the <slash> character, the effect is implementation-defined.
> 
> In my implementation "implementation-defined" means, that the leading
> slash is necessary.
> 
> Hmm.  I guess I have to lift this restriction.  However, this will very
> likly result in "/sem-name" refering the same semaphore as "sem-name".

Ok, I fixed that in CVS.  The next test release will behave same as
Linux, with the only exception that backslashes and slashes are both
treated like slashes on Linux.  Given that a semaphore is backed by
a file on the filesystem under /dev/shm, that shouldn't be much of
a surprise.


HTH,
Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Project Co-Leader          cygwin AT cygwin DOT com
Red Hat

--
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/