2 .\" Copyright (c) 1980, 1990, 1993
3 .\" The Regents of the University of California. All rights reserved.
5 .\" This code is derived from software contributed to Berkeley by
6 .\" the Institute of Electrical and Electronics Engineers, Inc.
8 .\" Redistribution and use in source and binary forms, with or without
9 .\" modification, are permitted provided that the following conditions
11 .\" 1. Redistributions of source code must retain the above copyright
12 .\" notice, this list of conditions and the following disclaimer.
13 .\" 2. Redistributions in binary form must reproduce the above copyright
14 .\" notice, this list of conditions and the following disclaimer in the
15 .\" documentation and/or other materials provided with the distribution.
16 .\" 4. Neither the name of the University nor the names of its contributors
17 .\" may be used to endorse or promote products derived from this software
18 .\" without specific prior written permission.
20 .\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
21 .\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
22 .\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
23 .\" ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
24 .\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
25 .\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
26 .\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
27 .\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
28 .\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
29 .\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
32 .\" @(#)date.1 8.3 (Berkeley) 4/28/95
40 .Nd display or set date and time
44 .Op Fl r Ar seconds | Ar filename
53 .Op Cm + Ns Ar output_fmt
57 .Op Oo Oo Ar mm Oc Ar dd Oc Ar HH
58 .Ar MM Oo Oo Ar cc Oc Ar yy Oc Op Ar .ss
62 .Fl f Ar input_fmt new_date
63 .Op Cm + Ns Ar output_fmt
66 .Op Fl t Ar minutes_west
68 When invoked without arguments, the
70 utility displays the current date and time.
71 Otherwise, depending on the options specified,
73 will set the date and time or print it in a user-defined way.
77 utility displays the date and time read from the kernel clock.
78 When used to set the date and time,
79 both the kernel clock and the hardware clock are updated.
81 Only the superuser may set the date,
82 and if the system securelevel (see
85 the time may not be changed by more than 1 second.
87 The options are as follows:
90 Set the kernel's value for daylight saving time.
93 is non-zero, future calls
96 will return a non-zero for
101 as the format string to parse the
103 provided rather than using the default
116 Parsing is done using
119 Do not try to set the date.
120 This allows you to use the
122 flag in addition to the
124 option to convert one date format to another.
130 sets the time on all of the machines in the local group.
133 option suppresses this behavior and causes the time to be set only on the
136 Use RFC 2822 date and time output format. This is equivalent to use
137 .Dq Li %a, %d %b %Y \&%T %z
146 Print the date and time represented by
150 is the number of seconds since the Epoch
151 (00:00:00 UTC, January 1, 1970;
154 and can be specified in decimal, octal, or hex.
156 Print the date and time of the last modification of
158 .It Fl t Ar minutes_west
159 Set the system's value for minutes west of
162 specifies the number of minutes returned in
167 Display or set the date in
169 (Coordinated Universal) time.
171 Adjust (i.e., take the current date and display the result of the
172 adjustment; not actually set the date) the second, minute, hour, month
173 day, week day, month or year according to
177 is preceded with a plus or minus sign,
178 the date is adjusted forwards or backwards according to the remaining string,
179 otherwise the relevant part of the date is set.
180 The date can be adjusted as many times as required using these flags.
181 Flags are processed in the order given.
184 (rather than adjusting them),
185 seconds are in the range 0-59, minutes are in the range 0-59, hours are
186 in the range 0-23, month days are in the range 1-31, week days are in the
188 months are in the range 1-12 (Jan-Dec)
189 and years are in the range 80-38 or 1980-2038.
193 is numeric, one of either
202 must be used to specify which part of the date is to be adjusted.
204 The week day or month may be specified using a name rather than a
206 If a name is used with the plus
208 sign, the date will be put forwards
212 date that matches the given week day or month.
213 This will not adjust the date,
214 if the given week day or month is the same as the current one.
216 When a date is adjusted to a specific value or in units greater than hours,
217 daylight savings time considerations are ignored.
218 Adjustments in units of hours or less honor daylight saving time.
219 So, assuming the current date is March 26, 0:30 and that the DST adjustment
220 means that the clock goes forward at 01:00 to 02:00, using
222 will adjust the date to March 26, 2:30.
223 Likewise, if the date is October 29, 0:30 and the DST adjustment means that
224 the clock goes back at 02:00 to 01:00, using
226 will be necessary to reach October 29, 2:30.
228 When the date is adjusted to a specific value that does not actually exist
229 (for example March 26, 1:30 BST 2000 in the Europe/London timezone),
230 the date will be silently adjusted forwards in units of one hour until it
231 reaches a valid time.
232 When the date is adjusted to a specific value that occurs twice
233 (for example October 29, 1:30 2000),
234 the resulting timezone will be set so that the date matches the earlier of
237 It is not possible to adjust a date to an invalid absolute day, so using
239 .Fl v No 31d Fl v No 12m
240 will simply fail five months of the year.
241 It is therefore usual to set the month before setting the day; using
242 .Fl v No 12m Fl v No 31d
245 Adjusting the date by months is inherently ambiguous because
246 a month is a unit of variable length depending on the current date.
247 This kind of date adjustment is applied in the most intuitive way.
250 tries to preserve the day of the month.
251 If it is impossible because the target month is shorter than the present one,
252 the last day of the target month will be the result.
255 on May 31 will adjust the date to June 30, while using the same option
256 on January 30 will result in the date adjusted to the last day of February.
257 This approach is also believed to make the most sense for shell scripting.
258 Nevertheless, be aware that going forth and back by the same number of
259 months may take you to a different date.
261 Refer to the examples below for further details.
264 An operand with a leading plus
266 sign signals a user-defined format string
267 which specifies the format in which to display the date and time.
268 The format string may contain any of the conversion specifications
271 manual page, as well as any arbitrary text.
274 character is always output after the characters specified by
276 The format string for the default display is
279 If an operand does not have a leading plus sign, it is interpreted as
280 a value for setting the system's notion of the current date and time.
281 The canonical representation for setting the date and time is:
283 .Bl -tag -width Ds -compact -offset indent
287 prepended to the abbreviated year.
289 Year in abbreviated form
290 (e.g., 89 for 1989, 06 for 2006).
292 Numeric month, a number from 1 to 12.
294 Day, a number from 1 to 31.
296 Hour, a number from 0 to 23.
298 Minutes, a number from 0 to 59.
300 Seconds, a number from 0 to 61
301 (59 plus a maximum of two leap seconds).
304 Everything but the minutes is optional.
306 Time changes for Daylight Saving Time, standard time, leap seconds,
307 and leap years are handled automatically.
309 The following environment variables affect the execution of
313 The timezone to use when displaying dates.
314 The normal format is a pathname relative to
315 .Pa /usr/share/zoneinfo .
316 For example, the command
317 .Dq TZ=America/Los_Angeles date
318 displays the current time in California.
321 for more information.
324 .Bl -tag -width /var/log/messages -compact
325 .It Pa /var/log/messages
326 record of the user setting the time
331 utility exits 0 on success, 1 if unable to set the date, and 2
332 if able to set the local date, but unable to set it globally.
336 .Dl "date ""+DATE: %Y-%m-%d%nTIME: %H:%M:%S"""
339 .Bd -literal -offset indent
344 In the Europe/London timezone, the command:
346 .Dl "date -v1m -v+1y"
350 .Dl "Sun Jan 4 04:15:24 GMT 1998"
352 where it is currently
353 .Li "Mon Aug 4 04:15:24 BST 1997" .
357 .Dl "date -v1d -v3m -v0y -v-1d"
359 will display the last day of February in the year 2000:
361 .Dl "Tue Feb 29 03:18:00 GMT 2000"
365 .Dl "date -v3m -v30d -v0y -v-1m"
367 because there is no such date as the 30th of February.
371 .Dl "date -v1d -v+1m -v-1d -v-fri"
373 will display the last Friday of the month:
375 .Dl "Fri Aug 29 04:31:11 BST 1997"
377 where it is currently
378 .Li "Mon Aug 4 04:31:11 BST 1997" .
382 .Dl "date 0613162785"
385 .Dq Li "June 13, 1985, 4:27 PM" .
387 .Dl "date ""+%m%d%H%M%Y.%S"""
389 may be used on one machine to print out the date
390 suitable for setting on another.
398 without modifying the date.
402 .Dl "date -j -f ""%a %b %d %T %Z %Y"" ""`date`"" ""+%s"""
404 can be used to parse the output from
406 and express it in Epoch time.
410 synchronizes the time on many hosts, the setting of a new time value may
411 require more than a few seconds.
415 .Ql Network time being set .
417 .Ql Communication error with timed
418 occurs when the communication
425 As above, except for the second line, which is:
430 .Op Oo Oo Oo Oo Ar cc Oc Ar yy Oc Ar mm Oc Ar dd Oc Ar HH
433 .Sh LEGACY DIAGNOSTICS
434 When invoked in legacy mode, the following exit values are returned:
435 .Bl -tag -width X -compact
437 The date was written successfully
439 Unable to set the date
441 Able to set the local date, but unable to set it globally
444 For more information about legacy mode, see
454 .%T "TSP: The Time Synchronization Protocol for UNIX 4.3BSD"
461 utility is expected to be compatible with
464 .Fl d , f , j , n , r , t ,
467 options are all extensions to the standard.