xref: /freebsd-12.1/lib/libc/sys/utimensat.2 (revision e0e03233)
1.\"	$NetBSD: utimes.2,v 1.13 1999/03/22 19:45:11 garbled Exp $
2.\"
3.\" Copyright (c) 1990, 1993
4.\"	The Regents of the University of California.  All rights reserved.
5.\" Copyright (c) 2012, Jilles Tjoelker
6.\"
7.\" Redistribution and use in source and binary forms, with or without
8.\" modification, are permitted provided that the following conditions
9.\" are met:
10.\" 1. Redistributions of source code must retain the above copyright
11.\"    notice, this list of conditions and the following disclaimer.
12.\" 2. Redistributions in binary form must reproduce the above copyright
13.\"    notice, this list of conditions and the following disclaimer in the
14.\"    documentation and/or other materials provided with the distribution.
15.\" 3. Neither the name of the University nor the names of its contributors
16.\"    may be used to endorse or promote products derived from this software
17.\"    without specific prior written permission.
18.\"
19.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
20.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
21.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
22.\" ARE DISCLAIMED.  IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
23.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
24.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
25.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
26.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
27.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
28.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
29.\" SUCH DAMAGE.
30.\"
31.\"     @(#)utimes.2	8.1 (Berkeley) 6/4/93
32.\" $FreeBSD$
33.\"
34.Dd June 7, 2017
35.Dt UTIMENSAT 2
36.Os
37.Sh NAME
38.Nm futimens ,
39.Nm utimensat
40.Nd set file access and modification times
41.Sh LIBRARY
42.Lb libc
43.Sh SYNOPSIS
44.In sys/stat.h
45.Ft int
46.Fn futimens "int fd" "const struct timespec times[2]"
47.Ft int
48.Fo utimensat
49.Fa "int fd"
50.Fa "const char *path"
51.Fa "const struct timespec times[2]"
52.Fa "int flag"
53.Fc
54.Sh DESCRIPTION
55The access and modification times of the file named by
56.Fa path
57or referenced by
58.Fa fd
59are changed as specified by the argument
60.Fa times .
61The inode-change-time of the file is set to the current time.
62.Pp
63If
64.Fa path
65specifies a relative path,
66it is relative to the current working directory if
67.Fa fd
68is
69.Dv AT_FDCWD
70and otherwise relative to the directory associated with the file descriptor
71.Fa fd .
72.Pp
73The
74.Va tv_nsec
75field of a
76.Vt timespec
77structure
78can be set to the special value
79.Dv UTIME_NOW
80to set the current time, or to
81.Dv UTIME_OMIT
82to leave the time unchanged.
83In either case, the
84.Va tv_sec
85field is ignored.
86.Pp
87If
88.Fa times
89is
90.No non- Ns Dv NULL ,
91it is assumed to point to an array of two timespec structures.
92The access time is set to the value of the first element, and the
93modification time is set to the value of the second element.
94For file systems that support file birth (creation) times (such as
95.Dv UFS2 ) ,
96the birth time will be set to the value of the second element
97if the second element is older than the currently set birth time.
98To set both a birth time and a modification time,
99two calls are required; the first to set the birth time
100and the second to set the (presumably newer) modification time.
101Ideally a new system call will be added that allows the setting
102of all three times at once.
103If
104.Fa times
105is
106.Dv NULL ,
107this is equivalent to passing
108a pointer to an array of two timespec structures
109with both
110.Va tv_nsec
111fields set to
112.Dv UTIME_NOW .
113.Pp
114If both
115.Va tv_nsec
116fields are
117.Dv UTIME_OMIT ,
118the timestamps remain unchanged and
119no permissions are needed for the file itself,
120although search permissions may be required for the path prefix.
121The call may or may not succeed if the named file does not exist.
122.Pp
123If both
124.Va tv_nsec
125fields are
126.Dv UTIME_NOW ,
127the caller must be the owner of the file, have permission to
128write the file, or be the super-user.
129.Pp
130For all other values of the timestamps,
131the caller must be the owner of the file or be the super-user.
132.Pp
133The values for the
134.Fa flag
135argument of the
136.Fn utimensat
137system call
138are constructed by a bitwise-inclusive OR of flags from the following list,
139defined in
140.In fcntl.h :
141.Bl -tag -width indent
142.It Dv AT_SYMLINK_NOFOLLOW
143If
144.Fa path
145names a symbolic link, the symbolic link's times are changed.
146By default,
147.Fn utimensat
148changes the times of the file referenced by the symbolic link.
149.El
150.Sh RETURN VALUES
151.Rv -std
152.Sh COMPATIBILITY
153If the running kernel does not support this system call,
154a wrapper emulates it using
155.Xr fstatat 2 ,
156.Xr futimesat 2
157and
158.Xr lutimes 2 .
159As a result, timestamps will be rounded down to the nearest microsecond,
160.Dv UTIME_OMIT
161is not atomic and
162.Dv AT_SYMLINK_NOFOLLOW
163is not available with a path relative to a file descriptor.
164.Sh ERRORS
165These system calls will fail if:
166.Bl -tag -width Er
167.It Bq Er EACCES
168The
169.Fa times
170argument is
171.Dv NULL ,
172or both
173.Va tv_nsec
174values are
175.Dv UTIME_NOW ,
176and the effective user ID of the process does not
177match the owner of the file, and is not the super-user, and write
178access is denied.
179.It Bq Er EFAULT
180The
181.Fa times
182argument
183points outside the process's allocated address space.
184.It Bq Er EINVAL
185The
186.Va tv_nsec
187component of at least one of the values specified by the
188.Fa times
189argument has a value less than 0 or greater than 999999999 and is not equal to
190.Dv UTIME_NOW
191or
192.Dv UTIME_OMIT .
193.It Bq Er EIO
194An I/O error occurred while reading or writing the affected inode.
195.It Bq Er EPERM
196The
197.Fa times
198argument is not
199.Dv NULL
200nor are both
201.Va tv_nsec
202values
203.Dv UTIME_NOW ,
204nor are both
205.Va tv_nsec
206values
207.Dv UTIME_OMIT
208and the calling process's effective user ID
209does not match the owner of the file and is not the super-user.
210.It Bq Er EPERM
211The named file has its immutable or append-only flag set, see the
212.Xr chflags 2
213manual page for more information.
214.It Bq Er EROFS
215The file system containing the file is mounted read-only.
216.El
217.Pp
218The
219.Fn futimens
220system call
221will fail if:
222.Bl -tag -width Er
223.It Bq Er EBADF
224The
225.Fa fd
226argument
227does not refer to a valid descriptor.
228.El
229.Pp
230The
231.Fn utimensat
232system call
233will fail if:
234.Bl -tag -width Er
235.It Bq Er EACCES
236Search permission is denied for a component of the path prefix.
237.It Bq Er EBADF
238The
239.Fa path
240argument does not specify an absolute path and the
241.Fa fd
242argument is neither
243.Dv AT_FDCWD
244nor a valid file descriptor.
245.It Bq Er EFAULT
246The
247.Fa path
248argument
249points outside the process's allocated address space.
250.It Bq Er ELOOP
251Too many symbolic links were encountered in translating the pathname.
252.It Bq Er ENAMETOOLONG
253A component of a pathname exceeded
254.Dv NAME_MAX
255characters, or an entire path name exceeded
256.Dv PATH_MAX
257characters.
258.It Bq Er ENOENT
259The named file does not exist.
260.It Bq Er ENOTDIR
261A component of the path prefix is not a directory.
262.It Bq Er ENOTDIR
263The
264.Fa path
265argument is not an absolute path and
266.Fa fd
267is neither
268.Dv AT_FDCWD
269nor a file descriptor associated with a directory.
270.El
271.Sh SEE ALSO
272.Xr chflags 2 ,
273.Xr stat 2 ,
274.Xr symlink 2 ,
275.Xr utimes 2 ,
276.Xr utime 3 ,
277.Xr symlink 7
278.Sh STANDARDS
279The
280.Fn futimens
281and
282.Fn utimensat
283system calls are expected to conform to
284.St -p1003.1-2008 .
285.Sh HISTORY
286The
287.Fn futimens
288and
289.Fn utimensat
290system calls appeared in
291.Fx 10.3 .
292