1explain_lutimes(3) Library Functions Manual explain_lutimes(3)
2
6 explain_lutimes - explain lutimes(3) errors
7
9 #include <libexplain/lutimes.h>
10 const char *explain_lutimes(const char *pathname, const struct timeval
11 *data);
12 const char *explain_errno_lutimes(int errnum, const char *pathname,
13 const struct timeval *data);
14 void explain_message_lutimes(char *message, int message_size, const
15 char *pathname, const struct timeval *data);
16 void explain_message_errno_lutimes(char *message, int message_size, int
17 errnum, const char *pathname, const struct timeval *data);
18
20 These functions may be used to obtain explanations for errors returned
21 by the lutimes(3) system call.
22 explain_lutimes
24 const char *explain_lutimes(const char *pathname, const struct timeval
25 *data);
26 The explain_lutimes function is used to obtain an explanation of an
28 error returned by the lutimes(3) system call. The least the message
29 will contain is the value of strerror(errno), but usually it will do
30 much better, and indicate the underlying cause in more detail.
31 The errno global variable will be used to obtain the error value to be
33 decoded.
34 pathname
36 The original pathname, exactly as passed to the lutimes(3) sys‐
37 tem call.
38 data The original data, exactly as passed to the lutimes(3) system
40 call.
41 Returns:
43 The message explaining the error. This message buffer is shared
44 by all libexplain functions which do not supply a buffer in
45 their argument list. This will be overwritten by the next call
46 to any libexplain function which shares this buffer, including
47 other threads.
48 Note: This function is not thread safe, because it shares a return buf‐
50 fer across all threads, and many other functions in this library.
51 Example: This function is intended to be used in a fashion similar to
53 the following example:
54 if (lutimes(pathname, data) < 0)
55 {
56 fprintf(stderr, "%s\n", explain_lutimes(pathname, data));
57 exit(EXIT_FAILURE);
58 }
59 The above code example is available pre-packaged as the
61 explain_lutimes_or_die(3) function.
62 explain_errno_lutimes
64 const char *explain_errno_lutimes(int errnum, const char *pathname,
65 const struct timeval *data);
66 The explain_errno_lutimes function is used to obtain an explanation of
68 an error returned by the lutimes(3) system call. The least the message
69 will contain is the value of strerror(errno), but usually it will do
70 much better, and indicate the underlying cause in more detail.
71 errnum The error value to be decoded, usually obtained from the errno
73 global variable just before this function is called. This is
74 necessary if you need to call any code between the system call
75 to be explained and this function, because many libc functions
76 will alter the value of errno.
77 pathname
79 The original pathname, exactly as passed to the lutimes(3) sys‐
80 tem call.
81 data The original data, exactly as passed to the lutimes(3) system
83 call.
84 Returns:
86 The message explaining the error. This message buffer is shared
87 by all libexplain functions which do not supply a buffer in
88 their argument list. This will be overwritten by the next call
89 to any libexplain function which shares this buffer, including
90 other threads.
91 Note: This function is not thread safe, because it shares a return buf‐
93 fer across all threads, and many other functions in this library.
94 Example: This function is intended to be used in a fashion similar to
96 the following example:
97 if (lutimes(pathname, data) < 0)
98 {
99 int err = errno;
100 fprintf(stderr, "%s\n", explain_errno_lutimes(err, pathname,
101 data));
102 exit(EXIT_FAILURE);
103 }
104 The above code example is available pre-packaged as the
106 explain_lutimes_or_die(3) function.
107 explain_message_lutimes
109 void explain_message_lutimes(char *message, int message_size, const
110 char *pathname, const struct timeval *data);
111 The explain_message_lutimes function is used to obtain an explanation
113 of an error returned by the lutimes(3) system call. The least the mes‐
114 sage will contain is the value of strerror(errno), but usually it will
115 do much better, and indicate the underlying cause in more detail.
116 The errno global variable will be used to obtain the error value to be
118 decoded.
119 message The location in which to store the returned message. If a suit‐
121 able message return buffer is supplied, this function is thread
122 safe.
123 message_size
125 The size in bytes of the location in which to store the
126 returned message.
127 pathname
129 The original pathname, exactly as passed to the lutimes(3) sys‐
130 tem call.
131 data The original data, exactly as passed to the lutimes(3) system
133 call.
134 Example: This function is intended to be used in a fashion similar to
136 the following example:
137 if (lutimes(pathname, data) < 0)
138 {
139 char message[3000];
140 explain_message_lutimes(message, sizeof(message), pathname,
141 data);
142 fprintf(stderr, "%s\n", message);
143 exit(EXIT_FAILURE);
144 }
145 The above code example is available pre-packaged as the
147 explain_lutimes_or_die(3) function.
148 explain_message_errno_lutimes
150 void explain_message_errno_lutimes(char *message, int message_size, int
151 errnum, const char *pathname, const struct timeval *data);
152 The explain_message_errno_lutimes function is used to obtain an expla‐
154 nation of an error returned by the lutimes(3) system call. The least
155 the message will contain is the value of strerror(errno), but usually
156 it will do much better, and indicate the underlying cause in more
157 detail.
158 message The location in which to store the returned message. If a suit‐
160 able message return buffer is supplied, this function is thread
161 safe.
162 message_size
164 The size in bytes of the location in which to store the
165 returned message.
166 errnum The error value to be decoded, usually obtained from the errno
168 global variable just before this function is called. This is
169 necessary if you need to call any code between the system call
170 to be explained and this function, because many libc functions
171 will alter the value of errno.
172 pathname
174 The original pathname, exactly as passed to the lutimes(3) sys‐
175 tem call.
176 data The original data, exactly as passed to the lutimes(3) system
178 call.
179 Example: This function is intended to be used in a fashion similar to
181 the following example:
182 if (lutimes(pathname, data) < 0)
183 {
184 int err = errno;
185 char message[3000];
186 explain_message_errno_lutimes(message, sizeof(message), err,
187 pathname, data);
188 fprintf(stderr, "%s\n", message);
189 exit(EXIT_FAILURE);
190 }
191 The above code example is available pre-packaged as the
193 explain_lutimes_or_die(3) function.
194
196 lutimes(3)
197 modify file timestamps
198 explain_lutimes_or_die(3)
200 modify file timestamps and report errors
201
203 libexplain version 1.4
204 Copyright (C) 2013 Peter Miller
205 explain_lutimes(3)