Date: Fri, 13 Dec 2002 11:50:33 -0500 (EST) From: Garrett Wollman <wollman@lcs.mit.edu> To: Joe Kelsey <joek@mail.flyingcroc.net> Cc: freebsd-current@FreeBSD.ORG Subject: Re: Posix Semaphores in -CURRENT Message-ID: <200212131650.gBDGoXLj017598@khavrinen.lcs.mit.edu> In-Reply-To: <3DFA0DAC.2070801@mail.flyingcroc.net> References: <3DF8F08E.8050809@mail.flyingcroc.net> <3DFA0771.BDFC87A8@mindspring.com> <3DFA0DAC.2070801@mail.flyingcroc.net>
next in thread | previous in thread | raw e-mail | index | archive | help
<<On Fri, 13 Dec 2002 08:41:16 -0800, Joe Kelsey <joek@mail.flyingcroc.net> said: > So, is there some mechanism I am missing? Is there a layer between the > application calling sem_open and the kernel receiving the parameters > that strips it down to the last component? If there is a higher level > involved here, why is the low-level ksem_create function worrying about > embedded '/' characters? I find this rather puzzling. Speaking as a standards person, I can state with some certainty that *the name of a POSIX semaphore is intended to have path name semantics*. It is not required to be an actual path name, but there is a clear expectation that a quality implementation will do so. The POSIX developers saw these IPC objects as being analogous to shared memory objects or fifos, and did not see a compelling reason to invent an entirely new namespace for them. Stevens actually suggests an implementation of named semaphores in which the semaphore is represented by a file which contains the name (``key'') of an SVID semaphore. -GAWollman To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200212131650.gBDGoXLj017598>