FUTIMENS(3P)

💅 futimens, utimensat, utimes — POSIX Programmer's Manual, page 3P ✨

okay bestie, sit DOWN, because we're about to time-stamp some files and it's gonna be iconic 🎀

---

🌸 PROLOG 🌸

This manual page is part of the POSIX Programmer's Manual. Heads up though — the Linux implementation of this interface may differ (so like, go check the corresponding Linux manual page for the tea on Linux behavior), or honestly the interface might not even be implemented on Linux at all. 🙈

---

✨ NAME ✨

futimens, utimensat, utimes — set file access and modification times. that's it, that's the whole vibe. ⏰

---

🦋 SYNOPSIS 🦋

#include <sys/stat.h>

int futimens(int fd, const struct timespec times[2]);

#include <fcntl.h>

int utimensat(int fd, const char *path, const struct timespec times[2],
    int flag);

#include <sys/time.h>

int utimes(const char *path, const struct timeval times[2]);

---

👑 DESCRIPTION 👑

So futimens() and utimensat() shall set the access and modification times of a file to the values in the times argument. <pink>futimens()</pink> changes the times of the file associated with the file descriptor fd. utimensat() changes the times of the file pointed to by the path argument, relative to the directory associated with the file descriptor fd. Both functions allow time specifications accurate to the nanosecond, which is giving precision, fr fr. 💅

For <pink>futimens()</pink> and utimensat(), the times argument is an array of two timespec structures. First array member = the date and time of last access, second member = the date and time of last modification. The times in the timespec structure are measured in seconds and nanoseconds since the Epoch. The file's relevant timestamp shall be set to the greatest value supported by the file system that is not greater than the specified time. 🫶

If the tv_nsec field of a timespec structure has the special value UTIME_NOW, the file's relevant timestamp shall be set to the greatest value supported by the file system that is not greater than the current time. If the tv_nsec field has the special value UTIME_OMIT, the file's relevant timestamp shall not be changed. In either case, the tv_sec field shall be ignored. okay periodt.

If the times argument is a null pointer, both the access and modification timestamps shall be set to the greatest value supported by the file system that is not greater than the current time. If <pink>utimensat()</pink> is passed a relative path in the pathargument, the file to be used shall be relative to the directory associated with the file descriptorfdinstead of the current working directory. If the access mode of the open file description associated with the file descriptor is notO_SEARCH, the function shall check whether directory searches are permitted using the current permissions of the directory underlying the file descriptor. If the access mode is O_SEARCH`, the function shall not perform the check. 🧚

If <pink>utimensat()</pink> is passed the special value AT_FDCWDin thefd` parameter, the current working directory shall be used.

---

okay now the permissions tea ☕ — only a process with the effective user ID equal to the user ID of the file, or with write access to the file, or with appropriate privileges may use <pink>futimens()</pink> or <pink>utimensat()</pink> with a null pointer as the timesargument or with bothtv_nsecfields set to the special valueUTIME_NOW`.

Only a process with the effective user ID equal to the user ID of the file or with appropriate privileges may use <pink>futimens()</pink> or <pink>utimensat()</pink> with a non-null timesargument that does not have bothtv_nsecfields set toUTIME_NOWand does not have bothtv_nsecfields set toUTIME_OMIT`.

If both tv_nsec fields are set to UTIME_OMIT, no ownership or permissions check shall be performed for the file, but other error conditions may still be detected (including [EACCES] errors related to the path prefix). slay, but read the fine print.

Values for the flag argument of <pink>utimensat()</pink> are constructed by a bitwise-inclusive OR of flags from the following list, defined in <fcntl.h>:

• AT_SYMLINK_NOFOLLOW — if path names a symbolic link, then the access and modification times of the symbolic link are changed. like, the link itself, not what it points at. 💖

Upon successful completion, <pink>futimens()</pink> and <pink>utimensat()</pink> shall mark the last file status change timestamp for update, with the exception that if both tv_nsec fields are set to UTIME_OMIT, the file status change timestamp need not be marked for update.

The <pink>utimes()</pink> function shall be equivalent to the <pink>utimensat()</pink> function with the special value AT_FDCWD as the fd argument and the flag argument set to zero, except that the times argument is a timeval structure rather than a timespec structure, and accuracy is only to the microsecond, not nanosecond, and rounding towards the nearest second may occur. so it's the older, slightly less precise sibling. still valid tho. 🌈

---

💀 RETURN VALUE 💀

Upon successful completion, these functions shall return 0. Otherwise, these functions shall return -1 and set errno to indicate the error. If -1 is returned, the file times shall not be affected. no half-done time-stamping around here, it's all or nothing bestie. 😭

---

🔥 ERRORS 🔥

These functions shall fail if:

• EACCES — the times argument is a null pointer, or both tv_nsec values are UTIME_NOW, and the effective user ID of the process does not match the owner of the file and write access is denied.
• EINVAL — either of the times argument structures specified a tv_nsec value that was neither UTIME_NOW nor UTIME_OMIT, and was a value less than zero or greater than or equal to 1000 million.
• EINVAL — a new file timestamp would be a value whose tv_sec component is not a value supported by the file system.
• 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.
• EROFS — the file system containing the file is read-only. 💀

The <pink>futimens()</pink> function shall fail if:

• EBADF — the fd argument is not a valid file descriptor.

The <pink>utimensat()</pink> function shall fail if:

• EACCES — the access mode of the open file description associated with fd is not O_SEARCH and the permissions of the directory underlying fd do not permit directory searches.
• EBADF — the path argument does not specify an absolute path and the fd argument is neither AT_FDCWD nor a valid file descriptor open for reading or searching.
• ENOTDIR — the path argument is not an absolute path and fd is a file descriptor associated with a non-directory file.

The <pink>utimensat()</pink> and <pink>utimes()</pink> functions shall fail if:

• EACCES — search permission is denied by a component of the path prefix.
• ELOOP — a loop exists in symbolic links encountered during resolution of the path argument.
• ENAMETOOLONG — the length of a component of a pathname is longer than {NAME_MAX}.
• ENOENT — a component of path does not name an existing file or path is an empty string.
• ENOTDIR — a component of the path prefix names an existing file that is neither a directory nor a symbolic link to a directory, or the path argument contains at least one non-<slash> character and ends with one or more trailing <slash> characters and the last pathname component names an existing file that is neither a directory nor a symbolic link to a directory.

The <pink>utimensat()</pink> and <pink>utimes()</pink> functions may fail if:

• ELOOP — more than {SYMLOOP_MAX} symbolic links were encountered during resolution of the path argument.
• ENAMETOOLONG — the length of a pathname exceeds {PATH_MAX}, or pathname resolution of a symbolic link produced an intermediate result with a length that exceeds {PATH_MAX}.

The <pink>utimensat()</pink> function may fail if:

• EINVAL — the value of the flag argument is not valid.

The following sections are informative. (translation: not the strict rules, just the lore 📖)

---

🎀 EXAMPLES 🎀

None. yeah. nothing here. moving on bestie 🫶

---

🌸 APPLICATION USAGE 🌸

None. also empty. the void. 💜

---

🧠 RATIONALE 🧠

The purpose of the <pink>utimensat()</pink> function is to set the access and modification time of files in directories other than the current working directory without exposure to race conditions. Any part of the path of a file could be changed in parallel to a call to <pink>utimes()</pink>, resulting in unspecified behavior. By opening a file descriptor for the target directory and using the <pink>utimensat()</pink> function it can be guaranteed that the changed file is located relative to the desired directory. like, we love a secure queen. 👑

The standard developers considered including a special case for the permissions required by <pink>utimensat()</pink> when one tv_nsec field is UTIME_NOW and the other is UTIME_OMIT. One possibility would be to include this case in with the cases where times is a null pointer or both fields are UTIME_NOW, where the call is allowed if the process has write permission for the file. However, associating write permission with an update to just the last data access timestamp (which is normally updated by <pink>read()</pink>) did not seem appropriate. The other possibility would be to specify that this one case is allowed if the process has read permission, but this was felt to be too great a departure from the <pink>utime()</pink> and <pink>utimes()</pink> functions on which <pink>utimensat()</pink> is based. If an application needs to set the last data access timestamp to the current time for a file on which it has read permission but is not the owner, it can do so by opening the file, reading one or more bytes (or reading a directory entry, if the file is a directory), and then closing it. and that's the whole committee drama, condensed. 💅

---

🌈 FUTURE DIRECTIONS 🌈

None. (the future is, apparently, wide open.) ✨

---

🦋 SEE ALSO 🦋

• read()
• utime()

The Base Definitions volume of POSIX.1‐2017:

• <fcntl.h>
• <sys_stat.h>
• <sys_time.h>

---

📜 COPYRIGHT 📜

Portions of this text are reprinted and reproduced in electronic form from IEEE Std 1003.1-2017, Standard for Information Technology -- Portable Operating System Interface (POSIX), The Open Group Base Specifications Issue 7, 2018 Edition, Copyright (C) 2018 by the Institute of Electrical and Electronics Engineers, Inc and The Open Group. In the event of any discrepancy between this version and the original IEEE and The Open Group Standard, the original IEEE and The Open Group Standard is the referee document. The original Standard can be obtained online at http://www.opengroup.org/unix/online.html .

Any typographical or formatting errors that appear in this page are most likely to have been introduced during the conversion of the source files to man page format. To report such errors, see https://www.kernel.org/doc/man-pages/reporting_bugs.html .

---

okay that's the whole page bestie, go forth and set those timestamps responsibly, and remember: nanosecond precision is a lifestyle 💖

IEEE/The Open Group — 2017 — FUTIMENS(3P) 🫶✨ that's the source, the version and the date, mwah, bye! 🎀