aboutsummaryrefslogtreecommitdiffstats
path: root/man2
diff options
context:
space:
mode:
authorMichael Kerrisk <mtk.manpages@gmail.com>2016-09-12 07:29:15 +0100
committerMichael Kerrisk <mtk.manpages@gmail.com>2016-09-12 07:39:40 +0100
commitddf5e4ab24086f80ee6f86bd154dfadae166a95d (patch)
tree89a920ed58d24a97a79e19879b7d5eff993878d0 /man2
parent40169a93c1d952460d1f6b1e3c441c11783f4ba9 (diff)
downloadman-pages-ddf5e4ab24086f80ee6f86bd154dfadae166a95d.tar.gz
open.2: Clarify the rules about how the group ID of a new file is determined
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
Diffstat (limited to 'man2')
-rw-r--r--man2/open.215
1 files changed, 10 insertions, 5 deletions
diff --git a/man2/open.2 b/man2/open.2
index 016c3cf4d2..28b92954f2 100644
--- a/man2/open.2
+++ b/man2/open.2
@@ -244,14 +244,19 @@ If the file does not exist, it will be created.
The owner (user ID) of the new file is set to the effective user ID
of the process.
-The group ownership (group ID) is set either to
-the effective group ID of the process or to the group ID of the
-parent directory (depending on filesystem type and mount options,
-and the mode of the parent directory; see the mount options
+
+The group ownership (group ID) of the new file is set either to
+the effective group ID of the process (System V semantics)
+or to the group ID of the parent directory (BSD semantics).
+On Linux, the behavior depends on whether the
+set-group-ID mode bit is set on the parent directory:
+if that bit is set, then BSD semantics apply;
+otherwise, System V semantics apply.
+For some filesystems, the behavior also depends on the
.I bsdgroups
and
.I sysvgroups
-described in
+mount options described in
.BR mount (8)).
.\" As at 2.6.25, bsdgroups is supported by ext2, ext3, ext4, and
.\" XFS (since 2.6.14).