Michael Kerrisk <michael.kerrisk@gmail.com> wrote, on 14 May 2008:
@ page 969 line 32433 section futimens comment {utimensat-errs}
[snip]
Lines 32400-32403 of the draft say :
Only a process with the effective user ID equal to the user ID
of the file or with appropriate privileges may use futimens() or
utimensat() with a non-null times argument that does not have both
tv_nsec fields set to UTIME_NOW and does not have both tv_nsec
fields set to UTIME_OMIT.
Looking at these lines suggests that the text for the EPERM error
should remove discussion of write access to the file, since the error
applies regardless of whether the file is writable.
Action:
Replace lines 32431 to 32435 with the following:
[EPERM] The times argument is not a null pointer, does not have both
tv_nsec fields set to UTIME_NOW, does not have both tv_nsec fields
set to UTIME_OMIT, the calling process' effective user ID does not
match the owner of the file, and the calling process does not have
appropriate privileges.
I agree that this change is needed. Since draft 5.1 has already been
produced, I suggest that we should take this as an aardvark against 5.1
(the page and line numbers are the same), to be addressed in TC1.
Do I need to do anything to get that Aardvark moved to the TC1 queue?