chmod.2, fsync.2, mkdir.2, mknod.2, open.2, truncate.2, umask.2, utime.2, utimensat.2: Add/replace references to inode(7)

Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
This commit is contained in:
Michael Kerrisk 2017-04-22 22:05:37 +02:00
parent 3b363b623c
commit e6fc15962c
9 changed files with 14 additions and 11 deletions

View File

@ -172,7 +172,7 @@ On some filesystems, only the superuser can set the sticky bit,
which may have a special meaning.
For the sticky bit, and for set-user-ID and set-group-ID bits on
directories, see
.BR stat (2).
.BR inode (7).
On NFS filesystems, restricting the permissions will immediately influence
already open files, because the access control is done on the server, but
@ -371,5 +371,6 @@ argument.
.BR execve (2),
.BR open (2),
.BR stat (2),
.BR inode (7),
.BR path_resolution (7),
.BR symlink (7)

View File

@ -71,7 +71,7 @@ was rebooted.
This includes writing through or flushing a disk cache if present.
The call blocks until the device reports that the transfer has completed.
It also flushes metadata information associated with the file (see
.BR stat (2)).
.BR inode (7)).
Calling
.BR fsync ()
@ -93,7 +93,7 @@ or
.I st_mtime
(respectively, time of last access and
time of last modification; see
.BR stat (2))
.BR inode (7))
do not require flushing because they are not necessary for
a subsequent data read to be handled correctly.
On the other hand, a change to the file size

View File

@ -52,7 +52,7 @@ attempts to create a directory named
The argument
.I mode
specifies the mode for the new directory (see
.BR stat (2)).
.BR inode (7)).
It is modified by the process's
.I umask
in the usual way: in the absence of a default ACL, the mode of the

View File

@ -62,7 +62,7 @@ argument specifies both the file mode to use and the type of node
to be created.
It should be a combination (using bitwise OR) of one of the file types
listed below and zero or more of the file mode bits listed in
.BR stat (2).
.BR inode (7).
The file mode is modified by the process's
.I umask

View File

@ -350,11 +350,11 @@ On Linux, the following bits are also honored in
.TP
.B S_ISGID
0002000 set-group-ID bit (see
.BR stat (2))
.BR inode (7)).
.TP
.B S_ISVTX
0001000 sticky bit (see
.BR stat (2))
.BR inode (7)).
.RE
.TP
.BR O_DIRECT " (since Linux 2.4.10)"

View File

@ -99,7 +99,7 @@ The file offset is not changed.
If the size changed, then the st_ctime and st_mtime fields
(respectively, time of last status change and
time of last modification; see
.BR stat (2))
.BR inode (7))
for the file are updated,
and the set-user-ID and set-group-ID mode bits may be cleared.
.LP

View File

@ -81,8 +81,8 @@ argument of 0666 (rw-rw-rw-), the resulting file permissions would be 0644
The constants that should be used to specify
.I mask
are described under
.BR stat (2).
are described in
.BR inode (7).
The typical default value for the process umask is
.I S_IWGRP\ |\ S_IWOTH

View File

@ -189,4 +189,5 @@ on an append-only file.
.BR stat (2),
.BR utimensat (2),
.BR futimens (3),
.BR futimes (3)
.BR futimes (3),
.BR inode (7)

View File

@ -639,5 +639,6 @@ instead checks whether the
.BR stat (2),
.BR utimes (2),
.BR futimes (3),
.BR inode (7),
.BR path_resolution (7),
.BR symlink (7)