shmget.2: Move and rework discussion of mode bits

Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
This commit is contained in:
Michael Kerrisk 2014-04-28 07:00:11 +02:00
parent fbaf6d6e17
commit e1d802d526
1 changed files with 10 additions and 10 deletions

View File

@ -106,16 +106,6 @@ This flag is used with
to ensure that this call creates the segment.
If the segment already exists, the call fails.
.TP
.I mode_flags
(least significant 9 bits)
specifying the permissions granted to the owner, group, and world.
These bits have the same format, and the same
meaning, as the
.I mode
argument of
.BR open (2).
Presently, the execute permissions are not used by the system.
.TP
.BR SHM_HUGETLB " (since Linux 2.6)"
Allocate the segment using "huge pages."
See the Linux kernel source file
@ -141,6 +131,16 @@ in
.\" As at 2.6.17-rc2, this flag has no effect if SHM_HUGETLB was also
.\" specified.
.PP
In addition to the above flags, the least significant 9 bits of
.I shmflg
specify the permissions granted to the owner, group, and others.
These bits have the same format, and the same
meaning, as the
.I mode
argument of
.BR open (2).
Presently, execute permissions are not used by the system.
.PP
When a new shared memory segment is created,
its contents are initialized to zero values, and
its associated data structure,