On Fri, Dec 13, 2002 at 08:41:16AM -0800, Joe Kelsey wrote: > >>portabliity issue as TRU64 (at least) allows arbitrary pathnames as > >>sempahores, probably storing some sort of marker in the directories (I > >>get this only from examining the TRU64 online manual pages at > >>>http://www.tru64unix.compaq.com/docs/base_doc/DOCUMENTATION/HTML/APS33DTE_html/DOCU_010.HTM
If you are going to argue about what FreeBSD should do, then in addition to checking with the TRU64 manual (TRU64 is probably in its sunset stage: http://news.com.com/2100-1001-976211.html), you should also refer to the POSIX standard: http://www.opengroup.org/onlinepubs/007904975/ For the man page for sem_open(), there is this: sem_t *sem_open(const char *name, int oflag, ...); "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." So apart from the leading slash character, nothing is mentioned about embedded slashes in the semaphore name. What's the right behavior for FreeBSD then? -- Craig Rodrigues http://www.gis.net/~craigr [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message