diff options
Diffstat (limited to 'man2/shmctl.2')
| -rw-r--r-- | man2/shmctl.2 | 35 |
1 files changed, 18 insertions, 17 deletions
diff --git a/man2/shmctl.2 b/man2/shmctl.2 index d13240647..06ee35d14 100644 --- a/man2/shmctl.2 +++ b/man2/shmctl.2 @@ -80,12 +80,12 @@ Size in bytes of the shared memory segment. .TP .I shm_atime Time of the last -.BR shmat (2) +.MR shmat 2 system call that attached this segment. .TP .I shm_dtime Time of the last -.BR shmdt (2) +.MR shmdt 2 system call that detached tgis segment. .TP .I shm_ctime @@ -99,9 +99,9 @@ ID of the process that created the shared memory segment. .TP .I shm_lpid ID of the last process that executed a -.BR shmat (2) +.MR shmat 2 or -.BR shmdt (2) +.MR shmdt 2 system call on this segment. .TP .I shm_nattch @@ -147,7 +147,7 @@ l l. Bits 0100, 0010, and 0001 (the execute bits) are unused by the system. (It is not necessary to have execute permission on a segment in order to perform a -.BR shmat (2) +.MR shmat 2 call with the .B SHM_EXEC flag.) @@ -212,7 +212,7 @@ otherwise its pages that were faulted in will remain in memory or swap. See also the description of .I /proc/sys/kernel/shm_rmid_forced in -.BR proc (5). +.MR proc 5 . .TP .BR IPC_INFO " (Linux-specific)" Return information about system-wide shared memory limits and @@ -251,7 +251,7 @@ and settings can be changed via .I /proc files of the same name; see -.BR proc (5) +.MR proc 5 for details. .TP .BR SHM_INFO " (Linux-specific)" @@ -338,7 +338,7 @@ if its effective UID matches the owner or creator UID of the segment, and the amount of memory to be locked falls within the .B RLIMIT_MEMLOCK resource limit (see -.BR setrlimit (2)). +.MR setrlimit 2 ). .\" There was some weirdness in Linux 2.6.9: SHM_LOCK and SHM_UNLOCK could .\" be applied to a segment, regardless of ownership of the segment. .\" This was a botch-up in the move to RLIMIT_MEMLOCK, and was fixed @@ -411,7 +411,7 @@ the limit for the real user ID of the calling process. This limit is defined by the .B RLIMIT_MEMLOCK soft resource limit (see -.BR setrlimit (2)). +.MR setrlimit 2 ). .TP .B EOVERFLOW \fBIPC_STAT\fP is attempted, and the GID or UID value @@ -443,7 +443,8 @@ capability). is 0 and the caller is not privileged.) .SH VERSIONS Linux permits a process to attach -.RB ( shmat (2)) +\%(\c +.MR shmat 2 ) a shared memory segment that has already been marked for deletion using .IR shmctl(IPC_RMID) . @@ -476,15 +477,15 @@ The and .B SHM_INFO operations are used by the -.BR ipcs (1) +.MR ipcs 1 program to provide information on allocated resources. In the future, these may modified or moved to a .I /proc filesystem interface. .SH SEE ALSO -.BR mlock (2), -.BR setrlimit (2), -.BR shmget (2), -.BR shmop (2), -.BR capabilities (7), -.BR sysvipc (7) +.MR mlock 2 , +.MR setrlimit 2 , +.MR shmget 2 , +.MR shmop 2 , +.MR capabilities 7 , +.MR sysvipc 7 |