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

msgop.2: Clarify wording of MSGMAX and MSGMNB limits 

Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
This commit is contained in:
Michael Kerrisk 2015-01-29 12:11:15 +01:00
parent 4b139190f9
commit faeaa68cca
1 changed files with 10 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

18
man2/msgop.2
View File

@ -517,23 +517,25 @@ The following limits on message queue resources affect the
call:
.TP
.B MSGMAX
Maximum size for a message text: 8192 bytes
(on Linux, this limit can be read and modified via
.IR /proc/sys/kernel/msgmax ).
Maximum size of a message text, in bytes (default value: 8192 bytes).
On Linux, this limit can be read and modified via
.IR /proc/sys/kernel/msgmax .
.TP
.B MSGMNB
Default maximum size in bytes of a message queue: 16384 bytes
(on Linux, this limit can be read and modified via
.IR /proc/sys/kernel/msgmnb ).
Maximum number of bytes that can be held in a message queue
(default value: 16384 bytes).
On Linux, this limit can be read and modified via
.IR /proc/sys/kernel/msgmnb .
A privileged process
(Linux: a process with the
.B CAP_SYS_RESOURCE
capability)
can increase the size of a message queue beyond
.B MSGMNB
by a
using the
.BR msgctl (2)
system call.
.B IPC_SET
operation.
.PP
The implementation has no intrinsic system-wide limits on the
number of message headers