Date: Fri, 27 Aug 2004 17:54:38 +0400 From: Wartan Hachaturow <wart@tepkom.ru> To: Tilman Linneweh <arved@FreeBSD.org> Cc: freebsd-standards@FreeBSD.org Subject: Re: kern/46239: posix semaphore implementation errors Message-ID: <20040827135438.GA16102@velvet.po.cs.msu.su> In-Reply-To: <200408271305.i7RD5Fos058444@freefall.freebsd.org> References: <200408271305.i7RD5Fos058444@freefall.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Aug 27, 2004 at 01:05:15PM +0000, Tilman Linneweh wrote: > Over to standards to check, if we violate POSIX here. > http://www.freebsd.org/cgi/query-pr.cgi?pr=46239 IEEE Std 1003.1, 2004 Edition: "The name argument points to a string naming a semaphore object. It is unspecified whether the name appears in the file system and is visible to functions that take pathnames as arguments. The name argument conforms to the construction rules for a pathname. 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. The interpretation of slash characters other than the leading slash character in name is implementation-defined." Standart defines only the leading "/" behaviour, and leaves other places of slash for the implementation to define. We define it like "we disallow slashes in other places". We even document it in BUGS section of the manpage :) -- Regards, Wartan. "Be different: conform."
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040827135438.GA16102>