LDP
/
man-pages
mirror of https://github.com/mkerrisk/man-pages
0
1
Fork 0
Code Releases Activity

ipc.7 --> svipc.7

This commit is contained in:
Michael Kerrisk 2006-04-21 03:53:43 +00:00
parent 9fe4bb75f5
commit 2c5e151c7f
12 changed files with 31 additions and 21 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
man2/msgctl.2
View File

@ -329,5 +329,5 @@ SVr4, SVID. SVID does not document the EIDRM error condition.
.BR msgrcv (2),
.BR msgsnd (2),
.BR capabilities (7),
.BR ipc (7),
.BR mq_overview (7)
.BR mq_overview (7),
.BR svipc (7)

4
man2/msgget.2
View File

@ -216,5 +216,5 @@ on a message queue scheduled for deletion.
.BR msgsnd (2),
.BR ftok (3),
.BR capabilities (7),
.BR ipc (7),
.BR mq_overview (7)
.BR mq_overview (7),
.BR svipc (7)

4
man2/msgop.2
View File

@ -435,5 +435,5 @@ and for the system wide maximum size in bytes of the message pool
.BR msgrcv (2),
.BR msgsnd (2),
.BR capabilities (7),
.BR ipc (7),
.BR mq_overview (7)
.BR mq_overview (7),
.BR svipc (7)

4
man2/semctl.2
View File

@ -506,5 +506,5 @@ SVr4, SVID. SVr4 documents more error conditions EINVAL and EOVERFLOW.
.BR semget (2),
.BR semop (2),
.BR capabilities (7),
.BR ipc (7),
.BR sem_overview (7)
.BR sem_overview (7),
.BR svipc (7)

18
man2/semget.2
View File

@ -98,12 +98,22 @@ argument of
not meaningful for semaphores, and write permissions mean permission
to alter semaphore values).
.PP
The values of the semaphores in a newly created set are indeterminate.
(POSIX.1 is explicit on this point.)
Although Linux, like many other implementations,
initialises the semaphore values to 0,
a portable application cannot rely on this:
it should explicitly initialise the semaphores to the desired values.
.\" In truth, every one of the many implementations that I've tested sets
.\" the values to zero, but I suppose there is/was some obscure
.\" implementation out there that does not.
.PP
When creating a new semaphore set,
.BR semget ()
initialises the set's associated data structure
initialises the set's associated data structure,
.I semid_ds
(see
.BR semctl (2))
.BR semctl (2)),
as follows:
.IP
.I sem_perm.cuid
@ -271,5 +281,5 @@ ERANGE, EFAULT.
.BR semop (2),
.BR ftok (3),
.BR capabilities (7),
.BR ipc (7),
.BR sem_overview (7)
.BR sem_overview (7),
.BR svipc (7)

4
man2/semop.2
View File

@ -481,5 +481,5 @@ ENOSPC.
.BR semget (2),
.BR sigaction (2),
.BR capabilities (7),
.BR ipc (7),
.BR sem_overview (7)
.BR sem_overview (7),
.BR svipc (7)

2
man2/shmget.2
View File

@ -283,4 +283,4 @@ is a non-portable Linux extension.
.BR shmdt (2),
.BR ftok (3),
.BR capabilities (7),
.BR ipc (7)
.BR svipc (7)

2
man2/shmop.2
View File

@ -288,4 +288,4 @@ prototypes; glibc2 has
.BR shmctl (2),
.BR shmget (2),
.BR capabilities (7),
.BR ipc (7)
.BR svipc (7)

2
man3/ftok.3
View File

@ -97,4 +97,4 @@ and files on
.BR semget (2),
.BR shmget (2),
.BR stat (2),
.BR ipc (7)
.BR svipc (7)

2
man5/ipc.5
View File

@ -1,2 +1,2 @@
.so man7/ipc.7
.so man7/svipc.7
.\" FIXME . this link will eventually be removed (created Apr 2006)

2
man5/proc.5
View File

@ -1632,7 +1632,7 @@ providing similar information to that available via
.BR ipcs (1).
These files have headers and are formatted (one IPC object per line)
for easy understanding.
.BR ipc (7)
.BR svipc (7)
provides further background on the information shown by these files.
.TP
.I /proc/tty

4
man7/svipc.7
View File

@ -22,9 +22,9 @@
.\"
.\" FIXME There is now duplication of some of the information
.\" below in semctl.2, msgctl.2, and shmctl.2 -- MTK, Nov 04
.TH IPC 7 1993-11-01 "Linux 0.99.13" "Linux Programmer's Manual"
.TH SVIPC 7 1993-11-01 "Linux 0.99.13" "Linux Programmer's Manual"
.SH NAME
ipc \- System V interprocess communication mechanisms
svipc \- System V interprocess communication mechanisms
.SH SYNOPSIS
.nf
.B