clone.2, intro.2, ipc.2, msgctl.2, msgget.2, msgop.2, semctl.2, semget.2, semop.2, shmctl.2, shmget.2, shmop.2, ftok.3, proc.5, namespaces.7: Change reference to svipc(7) to sysvipc(7)

Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
This commit is contained in:
Michael Kerrisk 2019-06-25 06:38:01 +02:00
parent 880c105e22
commit 343cdc5ac9
15 changed files with 15 additions and 15 deletions

View File

@ -287,7 +287,7 @@ the calling process.
This flag is intended for the implementation of containers.
.IP
An IPC namespace provides an isolated view of System\ V IPC objects (see
.BR svipc (7))
.BR sysvipc (7))
and (since Linux 2.6.30)
.\" commit 7eafd7c74c3f2e67c27621b987b28397110d643f
.\" https://lwn.net/Articles/312232/

View File

@ -129,6 +129,6 @@ Note that these can be different from page to page!
.BR signal (7),
.BR socket (7),
.BR standards (7),
.BR svipc (7),
.BR symlink (7),
.BR sysvipc (7),
.BR time (7)

View File

@ -67,4 +67,4 @@ and so on really are implemented as separate system calls.
.BR shmctl (2),
.BR shmdt (2),
.BR shmget (2),
.BR svipc (7)
.BR sysvipc (7)

View File

@ -388,4 +388,4 @@ flag in
.BR msgsnd (2),
.BR capabilities (7),
.BR mq_overview (7),
.BR svipc (7)
.BR sysvipc (7)

View File

@ -246,4 +246,4 @@ would more clearly show its function.
.BR ftok (3),
.BR capabilities (7),
.BR mq_overview (7),
.BR svipc (7)
.BR sysvipc (7)

View File

@ -712,4 +712,4 @@ main(int argc, char *argv[])
.BR msgget (2),
.BR capabilities (7),
.BR mq_overview (7),
.BR svipc (7)
.BR sysvipc (7)

View File

@ -602,4 +602,4 @@ in Linux 4.6.
.BR semop (2),
.BR capabilities (7),
.BR sem_overview (7),
.BR svipc (7)
.BR sysvipc (7)

View File

@ -318,4 +318,4 @@ would more clearly show its function.
.BR ftok (3),
.BR capabilities (7),
.BR sem_overview (7),
.BR svipc (7)
.BR sysvipc (7)

View File

@ -551,5 +551,5 @@ if (semop(semid, sops, 2) == \-1) {
.BR sigaction (2),
.BR capabilities (7),
.BR sem_overview (7),
.BR svipc (7),
.BR sysvipc (7),
.BR time (7)

View File

@ -447,4 +447,4 @@ flag in
.BR shmget (2),
.BR shmop (2),
.BR capabilities (7),
.BR svipc (7)
.BR sysvipc (7)

View File

@ -419,4 +419,4 @@ would more clearly show its function.
.BR ftok (3),
.BR capabilities (7),
.BR shm_overview (7),
.BR svipc (7)
.BR sysvipc (7)

View File

@ -299,4 +299,4 @@ number of shared memory segments
.BR shmget (2),
.BR capabilities (7),
.BR shm_overview (7),
.BR svipc (7)
.BR sysvipc (7)

View File

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

View File

@ -5792,7 +5792,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 svipc (7)
.BR sysvipc (7)
provides further background on the information shown by these files.
.TP
.IR /proc/thread-self " (since Linux 3.17)"

View File

@ -332,7 +332,7 @@ See
.SS IPC namespaces (CLONE_NEWIPC)
IPC namespaces isolate certain IPC resources,
namely, System V IPC objects (see
.BR svipc (7))
.BR sysvipc (7))
and (since Linux 2.6.30)
.\" commit 7eafd7c74c3f2e67c27621b987b28397110d643f
.\" https://lwn.net/Articles/312232/