sem_init(3) and pshared

[Roy Marples <roy%marples.name@localhost>]

Hi List

After discussion with Joerg patching py-uwsgi to test sem_init(3) 
locking [1] we have come to the conclusion that our semaphore 
implementation does support process shared semaphores. As such I propose 
the following patch to the sem_init(3) man page.

Comments welcome. I propose that this is also pulled up to -5 and -6 
also.

Thanks

Roy

[1] http://lists.unbit.it/pipermail/uwsgi/2012-July/004451.html

Index: sem_init.3
===================================================================
RCS file: /cvsroot/src/lib/librt/sem_init.3,v
retrieving revision 1.1
diff -u -p -r1.1 sem_init.3
--- sem_init.3  24 Jan 2003 01:52:44 -0000      1.1
+++ sem_init.3  10 Jul 2012 11:21:59 -0000
@@ -27,7 +27,7 @@
 .\" OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE,
 .\" EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
 .\"
-.Dd January 22, 2003
+.Dd July 10, 2003
 .Dt SEM_INIT 3
 .Os
 .Sh NAME
@@ -48,8 +48,7 @@ to have the value
 .Fa value .
 A non-zero value for
 .Fa pshared
-specifies a shared semaphore that can be used by multiple processes, which this
-implementation is not capable of.
+specifies a semaphore that can be shared between processes.
 .Pp
 Following a successful call to
 .Fn sem_init ,
@@ -86,14 +85,3 @@ Unable to initialize a shared semaphore.
 .Fn sem_init
 conforms to
 .St -p1003.1-96 .
-.Pp
-This implementation does not support shared semaphores, and reports this fact
-by setting
-.Va errno
-to
-.Er EPERM .
-This is perhaps a stretch of the intention of POSIX, but is
-compliant, with the caveat that
-.Fn sem_init
-always reports a permissions error when an attempt to create a shared semaphore
-is made.