1 .\" $NetBSD: utimes.2,v 1.13 1999/03/22 19:45:11 garbled Exp $
3 .\" Copyright (c) 1990, 1993
4 .\" The Regents of the University of California. All rights reserved.
6 .\" Redistribution and use in source and binary forms, with or without
7 .\" modification, are permitted provided that the following conditions
9 .\" 1. Redistributions of source code must retain the above copyright
10 .\" notice, this list of conditions and the following disclaimer.
11 .\" 2. Redistributions in binary form must reproduce the above copyright
12 .\" notice, this list of conditions and the following disclaimer in the
13 .\" documentation and/or other materials provided with the distribution.
14 .\" 3. Neither the name of the University nor the names of its contributors
15 .\" may be used to endorse or promote products derived from this software
16 .\" without specific prior written permission.
18 .\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
19 .\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
20 .\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
21 .\" ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
22 .\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
23 .\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
24 .\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
25 .\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
26 .\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
27 .\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
30 .\" @(#)utimes.2 8.1 (Berkeley) 6/4/93
41 .Nd set file access and modification times
47 .Fn utimes "const char *path" "const struct timeval *times"
49 .Fn lutimes "const char *path" "const struct timeval *times"
51 .Fn futimes "int fd" "const struct timeval *times"
53 .Fn futimesat "int fd" "const char *path" "const struct timeval times[2]"
56 These interfaces are obsoleted by
60 because they are not accurate to nanoseconds.
63 The access and modification times of the file named by
67 are changed as specified by the argument
74 the access and modification times are set to the current time.
75 The caller must be the owner of the file, have permission to
76 write the file, or be the super-user.
82 it is assumed to point to an array of two timeval structures.
83 The access time is set to the value of the first element, and the
84 modification time is set to the value of the second element.
85 For file systems that support file birth (creation) times (such as
87 the birth time will be set to the value of the second element
88 if the second element is older than the currently set birth time.
89 To set both a birth time and a modification time,
90 two calls are required; the first to set the birth time
91 and the second to set the (presumably newer) modification time.
92 Ideally a new system call will be added that allows the setting
93 of all three times at once.
94 The caller must be the owner of the file or be the super-user.
96 In either case, the inode-change-time of the file is set to the current
104 except in the case where the named file is a symbolic link,
107 changes the access and modification times of the link,
110 changes the times of the file the link references.
114 system call is equivalent to
116 except in the case where
118 specifies a relative path.
119 In this case the access and modification time
120 is set to that of a file relative to the directory associated with the file
123 instead of the current working directory.
126 is passed the special value
130 parameter, the current working directory is used and the behavior
131 is identical to a call to
136 All of the system call will fail if:
139 Search permission is denied for a component of the path prefix.
145 and the effective user ID of the process does not
146 match the owner of the file, and is not the super-user, and write
154 points outside the process's allocated address space.
159 points outside the process's allocated address space.
163 component of at least one of the values specified by the
165 argument has a value less than 0 or greater than 999999.
167 An I/O error occurred while reading or writing the affected inode.
169 Too many symbolic links were encountered in translating the pathname.
170 .It Bq Er ENAMETOOLONG
171 A component of a pathname exceeded
173 characters, or an entire path name exceeded
177 The named file does not exist.
179 A component of the path prefix is not a directory.
185 and the calling process's effective user ID
186 does not match the owner of the file and is not the super-user.
188 The named file has its immutable or append-only flags set.
191 manual page for more information.
193 The file system containing the file is mounted read-only.
205 does not refer to a valid descriptor.
208 In addition to the errors returned by the
217 argument does not specify an absolute path and the
221 nor a valid file descriptor open for searching.
225 argument is not an absolute path and
229 nor a file descriptor associated with a directory.
239 function is expected to conform to
243 system call follows The Open Group Extended API Set 2 specification
251 system call appeared in
257 system calls first appeared in
261 system call appeared in