[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: sem_open can't open a name with directory



Ulrich Drepper wrote:
Ulrich could justifiably reply with "So what?  That's not required by
the standard."
But it seems at least hospitable to allow programs written
to run properly under the Posix-compliant part of OSF-1
to continue running properly under the Posix-compliant part of Linux.

Programs depending on this are not portable and if the OSF manuals didn't warn you it's DEC's fault. The shared memory filesystem the semaphores are allocated in require real resources. And to guarantee stability: cleanup. The user does not have access to the directory and so over time many many directories could be accumulated.

I think your cleanup issue is an important one. Can we think of a way to satisfy that while still being compatible with OSF/1? For instance, what if you simply transform '/' characters in the semaphore name into '_' characters? Then no directories need be created, the namespaces is still under the runtime library's control, and everybody is happy.

In short, this policy is not in place for no reason.  Write portable
applications and you won't have problems.

You're certainly right -- but it wouldn't be hard to be right *and* hospitable, too, in this case :-) - Dan

--
Dan Kegel
http://www.kegel.com
http://counter.li.org/cgi-bin/runscript/display-person.cgi?user=78045





[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]