kern/46239: posix semaphore implementation errors

Wartan Hachaturow wart at
Fri Aug 27 06:57:27 PDT 2004

On Fri, Aug 27, 2004 at 01:05:15PM +0000, Tilman Linneweh wrote:
> Over to standards to check, if we violate POSIX here.

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

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."

More information about the freebsd-standards mailing list