mirror of https://github.com/mkerrisk/man-pages
ipc.7 --> svipc.7
This commit is contained in:
parent
9fe4bb75f5
commit
2c5e151c7f
|
@ -329,5 +329,5 @@ SVr4, SVID. SVID does not document the EIDRM error condition.
|
||||||
.BR msgrcv (2),
|
.BR msgrcv (2),
|
||||||
.BR msgsnd (2),
|
.BR msgsnd (2),
|
||||||
.BR capabilities (7),
|
.BR capabilities (7),
|
||||||
.BR ipc (7),
|
.BR mq_overview (7),
|
||||||
.BR mq_overview (7)
|
.BR svipc (7)
|
||||||
|
|
|
@ -216,5 +216,5 @@ on a message queue scheduled for deletion.
|
||||||
.BR msgsnd (2),
|
.BR msgsnd (2),
|
||||||
.BR ftok (3),
|
.BR ftok (3),
|
||||||
.BR capabilities (7),
|
.BR capabilities (7),
|
||||||
.BR ipc (7),
|
.BR mq_overview (7),
|
||||||
.BR mq_overview (7)
|
.BR svipc (7)
|
||||||
|
|
|
@ -435,5 +435,5 @@ and for the system wide maximum size in bytes of the message pool
|
||||||
.BR msgrcv (2),
|
.BR msgrcv (2),
|
||||||
.BR msgsnd (2),
|
.BR msgsnd (2),
|
||||||
.BR capabilities (7),
|
.BR capabilities (7),
|
||||||
.BR ipc (7),
|
.BR mq_overview (7),
|
||||||
.BR mq_overview (7)
|
.BR svipc (7)
|
||||||
|
|
|
@ -506,5 +506,5 @@ SVr4, SVID. SVr4 documents more error conditions EINVAL and EOVERFLOW.
|
||||||
.BR semget (2),
|
.BR semget (2),
|
||||||
.BR semop (2),
|
.BR semop (2),
|
||||||
.BR capabilities (7),
|
.BR capabilities (7),
|
||||||
.BR ipc (7),
|
.BR sem_overview (7),
|
||||||
.BR sem_overview (7)
|
.BR svipc (7)
|
||||||
|
|
|
@ -98,12 +98,22 @@ argument of
|
||||||
not meaningful for semaphores, and write permissions mean permission
|
not meaningful for semaphores, and write permissions mean permission
|
||||||
to alter semaphore values).
|
to alter semaphore values).
|
||||||
.PP
|
.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,
|
When creating a new semaphore set,
|
||||||
.BR semget ()
|
.BR semget ()
|
||||||
initialises the set's associated data structure
|
initialises the set's associated data structure,
|
||||||
.I semid_ds
|
.I semid_ds
|
||||||
(see
|
(see
|
||||||
.BR semctl (2))
|
.BR semctl (2)),
|
||||||
as follows:
|
as follows:
|
||||||
.IP
|
.IP
|
||||||
.I sem_perm.cuid
|
.I sem_perm.cuid
|
||||||
|
@ -271,5 +281,5 @@ ERANGE, EFAULT.
|
||||||
.BR semop (2),
|
.BR semop (2),
|
||||||
.BR ftok (3),
|
.BR ftok (3),
|
||||||
.BR capabilities (7),
|
.BR capabilities (7),
|
||||||
.BR ipc (7),
|
.BR sem_overview (7),
|
||||||
.BR sem_overview (7)
|
.BR svipc (7)
|
||||||
|
|
|
@ -481,5 +481,5 @@ ENOSPC.
|
||||||
.BR semget (2),
|
.BR semget (2),
|
||||||
.BR sigaction (2),
|
.BR sigaction (2),
|
||||||
.BR capabilities (7),
|
.BR capabilities (7),
|
||||||
.BR ipc (7),
|
.BR sem_overview (7),
|
||||||
.BR sem_overview (7)
|
.BR svipc (7)
|
||||||
|
|
|
@ -283,4 +283,4 @@ is a non-portable Linux extension.
|
||||||
.BR shmdt (2),
|
.BR shmdt (2),
|
||||||
.BR ftok (3),
|
.BR ftok (3),
|
||||||
.BR capabilities (7),
|
.BR capabilities (7),
|
||||||
.BR ipc (7)
|
.BR svipc (7)
|
||||||
|
|
|
@ -288,4 +288,4 @@ prototypes; glibc2 has
|
||||||
.BR shmctl (2),
|
.BR shmctl (2),
|
||||||
.BR shmget (2),
|
.BR shmget (2),
|
||||||
.BR capabilities (7),
|
.BR capabilities (7),
|
||||||
.BR ipc (7)
|
.BR svipc (7)
|
||||||
|
|
|
@ -97,4 +97,4 @@ and files on
|
||||||
.BR semget (2),
|
.BR semget (2),
|
||||||
.BR shmget (2),
|
.BR shmget (2),
|
||||||
.BR stat (2),
|
.BR stat (2),
|
||||||
.BR ipc (7)
|
.BR svipc (7)
|
||||||
|
|
|
@ -1,2 +1,2 @@
|
||||||
.so man7/ipc.7
|
.so man7/svipc.7
|
||||||
.\" FIXME . this link will eventually be removed (created Apr 2006)
|
.\" FIXME . this link will eventually be removed (created Apr 2006)
|
||||||
|
|
|
@ -1632,7 +1632,7 @@ providing similar information to that available via
|
||||||
.BR ipcs (1).
|
.BR ipcs (1).
|
||||||
These files have headers and are formatted (one IPC object per line)
|
These files have headers and are formatted (one IPC object per line)
|
||||||
for easy understanding.
|
for easy understanding.
|
||||||
.BR ipc (7)
|
.BR svipc (7)
|
||||||
provides further background on the information shown by these files.
|
provides further background on the information shown by these files.
|
||||||
.TP
|
.TP
|
||||||
.I /proc/tty
|
.I /proc/tty
|
||||||
|
|
|
@ -22,9 +22,9 @@
|
||||||
.\"
|
.\"
|
||||||
.\" FIXME There is now duplication of some of the information
|
.\" FIXME There is now duplication of some of the information
|
||||||
.\" below in semctl.2, msgctl.2, and shmctl.2 -- MTK, Nov 04
|
.\" 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
|
.SH NAME
|
||||||
ipc \- System V interprocess communication mechanisms
|
svipc \- System V interprocess communication mechanisms
|
||||||
.SH SYNOPSIS
|
.SH SYNOPSIS
|
||||||
.nf
|
.nf
|
||||||
.B
|
.B
|
||||||
|
|
Loading…
Reference in New Issue