Provided by: manpages-dev_3.24-1ubuntu1_all
futimesat - change timestamps of a file relative to a directory file
#include <fcntl.h> /* Definition of AT_* constants */
int futimesat(int dirfd, const char *pathname,
const struct timeval times);
Feature Test Macro Requirements for glibc (see feature_test_macros(7)):
Since glibc 2.10: _XOPEN_SOURCE >= 700 || _POSIX_C_SOURCE >= 200809L
Before glibc 2.10: _ATFILE_SOURCE
This system call is obsolete. Use utimensat(2) instead.
The futimesat() system call operates in exactly the same way as
utimes(2), except for the differences described in this manual page.
If the pathname given in pathname is relative, then it is interpreted
relative to the directory referred to by the file descriptor dirfd
(rather than relative to the current working directory of the calling
process, as is done by utimes(2) for a relative pathname).
If pathname is relative and dirfd is the special value AT_FDCWD, then
pathname is interpreted relative to the current working directory of
the calling process (like utimes(2)).
If pathname is absolute, then dirfd is ignored.
On success, futimesat() returns a 0. On error, -1 is returned and
errno is set to indicate the error.
The same errors that occur for utimes(2) can also occur for
futimesat(). The following additional errors can occur for
EBADF dirfd is not a valid file descriptor.
pathname is relative and dirfd is a file descriptor referring to
a file other than a directory.
futimesat() was added to Linux in kernel 2.6.16.
This system call is nonstandard. It was implemented from a
specification that was proposed for POSIX.1, but that specification was
replaced by the one for utimensat(2).
A similar system call exists on Solaris.
If pathname is NULL, then the glibc futimesat() wrapper function
updates the times for the file referred to by dirfd.
stat(2), utimensat(2), utimes(2), futimes(3), path_resolution(7)
This page is part of release 3.24 of the Linux man-pages project. A
description of the project, and information about reporting bugs, can
be found at http://www.kernel.org/doc/man-pages/.