d/freebsd-nq
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Sharing semaphores between processes works now, so remove the stale comments

Browse Source 
about it always returning EPERM. Document that ENFILE occurs when the
limit on kernel semaphores is reached.
This commit is contained in:
Tim J. Robbins 2003-01-14 04:12:33 +00:00
parent 1493ebe7db
commit ab099bd309
2 changed files with 16 additions and 32 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

24
lib/libc/gen/sem_init.3
View File

@ -26,7 +26,7 @@
.\" EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
.\"
.\" $FreeBSD$
.Dd February 15, 2000
.Dd January 14, 2003
.Dt SEM_INIT 3
.Os
.Sh NAME
@ -47,8 +47,9 @@ 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 shared semaphore that can be used by any process
that can access
.Fa sem .
.Pp
Following a successful call to
.Fn sem_init ,
@ -73,8 +74,10 @@ will fail if:
exceeds SEM_VALUE_MAX.
.It Bq Er ENOSPC
Memory allocation error.
.It Bq Er EPERM
Unable to initialize a shared semaphore.
.It Bq Er ENFILE
The system limit on semaphores
.Pq Dv SEM_NSEMS_MAX
has been reached.
.El
.Sh SEE ALSO
.Xr sem_destroy 3 ,
@ -86,14 +89,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.

24
lib/libc_r/man/sem_init.3
View File

@ -26,7 +26,7 @@
.\" EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
.\"
.\" $FreeBSD$
.Dd February 15, 2000
.Dd January 14, 2003
.Dt SEM_INIT 3
.Os
.Sh NAME
@ -47,8 +47,9 @@ 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 shared semaphore that can be used by any process
that can access
.Fa sem .
.Pp
Following a successful call to
.Fn sem_init ,
@ -73,8 +74,10 @@ will fail if:
exceeds SEM_VALUE_MAX.
.It Bq Er ENOSPC
Memory allocation error.
.It Bq Er EPERM
Unable to initialize a shared semaphore.
.It Bq Er ENFILE
The system limit on semaphores
.Pq Dv SEM_NSEMS_MAX
has been reached.
.El
.Sh SEE ALSO
.Xr sem_destroy 3 ,
@ -86,14 +89,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.