utimensat.2: ffix + wfix

Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
This commit is contained in:
Michael Kerrisk 2016-02-17 11:17:51 +01:00
parent 35acdc5d41
commit 47c3854b91
1 changed files with 6 additions and 10 deletions

View File

@ -240,11 +240,10 @@ or both
.I tv_nsec
values are
.BR UTIME_NOW ,
and:
.PD 0
and either:
.RS
.IP * 2
the effective user ID of the caller does not match
.IP * 3
the the effective user ID of the caller does not match
the owner of the file,
the caller does not have write access to the file,
and the caller is not privileged
@ -279,7 +278,6 @@ the file is marked immutable (see
.BR chattr (1)).
.\" EXT2_IMMUTABLE_FL and similar flags for other filesystems.
.RE
.PD
.TP
.B EBADF
.RB ( futimens ())
@ -378,10 +376,9 @@ and neither
.I tv_nsec
field is
.BR UTIME_OMIT )
and:
.PD 0
and either:
.RS
.IP * 2
.IP * 3
the caller's effective user ID does not match the owner of file,
and the caller is not privileged
(Linux: does not have the
@ -401,7 +398,6 @@ the file is marked append-only or immutable (see
.\" EACCES and EPERM, where only EPERM tests for append-only.
.\" (This was also so for the older utimes() implementation.)
.RE
.PD
.TP
.B EROFS
The file is on a read-only filesystem.
@ -491,7 +487,7 @@ and
on kernels before 2.6.26.
These bugs are either nonconformances with the POSIX.1 draft specification
or inconsistencies with historical Linux behavior.
.IP * 2
.IP * 3
POSIX.1 specifies that if one of the
.I tv_nsec
fields has the value