Date: Tue, 8 Dec 2009 23:10:28 +0100 From: Jilles Tjoelker <jilles@stack.nl> To: John Baldwin <jhb@freebsd.org> Cc: svn-src-head@freebsd.org, svn-src-all@freebsd.org, src-committers@freebsd.org Subject: Re: svn commit: r200274 - head/lib/libc/gen Message-ID: <20091208221028.GA57735@stack.nl> In-Reply-To: <200912081645.37356.jhb@freebsd.org> References: <200912082048.nB8Km6aP099420@svn.freebsd.org> <200912081645.37356.jhb@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Dec 08, 2009 at 04:45:37PM -0500, John Baldwin wrote: > On Tuesday 08 December 2009 3:48:06 pm Jilles Tjoelker wrote: > > Author: jilles > > Date: Tue Dec 8 20:48:06 2009 > > New Revision: 200274 > > URL: http://svn.freebsd.org/changeset/base/200274 > > Log: > > sem_init(3): document process shared semaphores and their restrictions > I think the other language was more accurate. The new language has > far less detail such as no longer documenting EPERM. It seems that EPERM longer happens, at least not for any process-shared semaphore at all. What's missing is the SIGSYS/ENOSYS you'll get if sem.ko is not loaded, and you're requesting a process-shared semaphore or not linking with the threading library. > I think it is also quite accurate to say that the current > implementation is not capable of process shared semaphores. Several > things would need to be changed including moving away from using file > descriptors. There are some lines of code dedicated to make it work, and some people seem to use it, although they notice that it does not work very well. This topic has come up on the mailing lists several times recently. -- Jilles Tjoelker
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20091208221028.GA57735>