1 .\" Copyright (c) 1980, 1990, 1993
2 .\" The Regents of the University of California. All rights reserved.
4 .\" This code is derived from software contributed to Berkeley by
5 .\" the Institute of Electrical and Electronics Engineers, Inc.
7 .\" Redistribution and use in source and binary forms, with or without
8 .\" modification, are permitted provided that the following conditions
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.
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
31 .\" @(#)date.1 8.3 (Berkeley) 4/28/95
32 .\" $FreeBSD: src/bin/date/date.1,v 1.72 2005/02/13 22:25:09 ru Exp $
39 .Nd display or set date and time
52 .Op Cm + Ns Ar output_fmt
56 .Op Oo Oo Oo Oo Ar cc Oc Ar yy Oc Ar mm Oc Ar dd Oc Ar HH
61 .Fl f Ar input_fmt new_date
62 .Op Cm + Ns Ar output_fmt
65 .Op Fl t Ar minutes_west
67 When invoked without arguments, the
69 utility displays the current date and time.
70 Otherwise, depending on the options specified,
72 will set the date and time or print it in a user-defined way.
76 utility displays the date and time read from the kernel clock.
77 When used to set the date and time,
78 both the kernel clock and the hardware clock are updated.
80 Only the superuser may set the date,
81 and if the system securelevel (see
84 the time may not be changed by more than 1 second.
86 The options are as follows:
89 Set the kernel's value for daylight saving time.
92 is non-zero, future calls
95 will return a non-zero for
100 as the format string to parse the
102 provided rather than using the default
113 Parsing is done using
116 Do not try to set the date.
117 This allows you to use the
119 flag in addition to the
121 option to convert one date format to another.
127 sets the time on all of the machines in the local group.
130 option suppresses this behavior and causes the time to be set only on the
133 Use RFC 2822 date and time output format. This is equivalent to use
134 .Dq Li %a, %d %b %Y \&%T %z
143 Print the date and time represented by
147 is the number of seconds since the Epoch
148 (00:00:00 UTC, January 1, 1970;
151 and can be specified in decimal, octal, or hex.
152 .It Fl t Ar minutes_west
153 Set the system's value for minutes west of
156 specifies the number of minutes returned in
161 Display or set the date in
163 (Coordinated Universal) time.
165 Adjust (i.e., take the current date and display the result of the
166 adjustment; not actually set the date) the second, minute, hour, month
167 day, week day, month or year according to
171 is preceded with a plus or minus sign,
172 the date is adjusted forwards or backwards according to the remaining string,
173 otherwise the relevant part of the date is set.
174 The date can be adjusted as many times as required using these flags.
175 Flags are processed in the order given.
178 (rather than adjusting them),
179 seconds are in the range 0-59, minutes are in the range 0-59, hours are
180 in the range 0-23, month days are in the range 1-31, week days are in the
182 months are in the range 1-12 (Jan-Dec)
183 and years are in the range 80-38 or 1980-2038.
187 is numeric, one of either
196 must be used to specify which part of the date is to be adjusted.
198 The week day or month may be specified using a name rather than a
200 If a name is used with the plus
202 sign, the date will be put forwards
206 date that matches the given week day or month.
207 This will not adjust the date,
208 if the given week day or month is the same as the current one.
210 When a date is adjusted to a specific value or in units greater than hours,
211 daylight savings time considerations are ignored.
212 Adjustments in units of hours or less honor daylight saving time.
213 So, assuming the current date is March 26, 0:30 and that the DST adjustment
214 means that the clock goes forward at 01:00 to 02:00, using
216 will adjust the date to March 26, 2:30.
217 Likewise, if the date is October 29, 0:30 and the DST adjustment means that
218 the clock goes back at 02:00 to 01:00, using
220 will be necessary to reach October 29, 2:30.
222 When the date is adjusted to a specific value that does not actually exist
223 (for example March 26, 1:30 BST 2000 in the Europe/London timezone),
224 the date will be silently adjusted forwards in units of one hour until it
225 reaches a valid time.
226 When the date is adjusted to a specific value that occurs twice
227 (for example October 29, 1:30 2000),
228 the resulting timezone will be set so that the date matches the earlier of
231 Adjusting the date by months is inherently ambiguous because
232 a month is a unit of variable length depending on the current date.
233 This kind of date adjustment is applied in the most intuitive way.
236 tries to preserve the day of the month.
237 If it is impossible because the target month is shorter than the present one,
238 the last day of the target month will be the result.
241 on May 31 will adjust the date to June 30, while using the same option
242 on January 30 will result in the date adjusted to the last day of February.
243 This approach is also believed to make the most sense for shell scripting.
244 Nevertheless, be aware that going forth and back by the same number of
245 months may take you to a different date.
247 Refer to the examples below for further details.
250 An operand with a leading plus
252 sign signals a user-defined format string
253 which specifies the format in which to display the date and time.
254 The format string may contain any of the conversion specifications
257 manual page, as well as any arbitrary text.
260 character is always output after the characters specified by
262 The format string for the default display is
265 If an operand does not have a leading plus sign, it is interpreted as
266 a value for setting the system's notion of the current date and time.
267 The canonical representation for setting the date and time is:
269 .Bl -tag -width Ds -compact -offset indent
273 prepended to the abbreviated year.
275 Year in abbreviated form
276 (e.g., 89 for 1989, 06 for 2006).
278 Numeric month, a number from 1 to 12.
280 Day, a number from 1 to 31.
282 Hour, a number from 0 to 23.
284 Minutes, a number from 0 to 59.
286 Seconds, a number from 0 to 61
287 (59 plus a maximum of two leap seconds).
290 Everything but the minutes is optional.
292 Time changes for Daylight Saving Time, standard time, leap seconds,
293 and leap years are handled automatically.
295 The following environment variables affect the execution of
299 The timezone to use when displaying dates.
300 The normal format is a pathname relative to
301 .Pa /usr/share/zoneinfo .
302 For example, the command
303 .Dq TZ=America/Los_Angeles date
304 displays the current time in California.
307 for more information.
310 .Bl -tag -width /var/log/messages -compact
312 record of date resets and time changes
313 .It Pa /var/log/messages
314 record of the user setting the time
319 utility exits 0 on success, 1 if unable to set the date, and 2
320 if able to set the local date, but unable to set it globally.
324 .Dl "date ""+DATE: %Y-%m-%d%nTIME: %H:%M:%S"""
327 .Bd -literal -offset indent
332 In the Europe/London timezone, the command:
334 .Dl "date -v1m -v+1y"
338 .Dl "Sun Jan 4 04:15:24 GMT 1998"
340 where it is currently
341 .Li "Mon Aug 4 04:15:24 BST 1997" .
345 .Dl "date -v1d -v3m -v0y -v-1d"
347 will display the last day of February in the year 2000:
349 .Dl "Tue Feb 29 03:18:00 GMT 2000"
351 So will do the command:
353 .Dl "date -v30d -v3m -v0y -v-1m"
355 because there is no such date as the 30th of February.
359 .Dl "date -v1d -v+1m -v-1d -v-fri"
361 will display the last Friday of the month:
363 .Dl "Fri Aug 29 04:31:11 BST 1997"
365 where it is currently
366 .Li "Mon Aug 4 04:31:11 BST 1997" .
370 .Dl "date 8506131627"
373 .Dq Li "June 13, 1985, 4:27 PM" .
375 .Dl "date ""+%Y%m%d%H%M.%S"""
377 may be used on one machine to print out the date
378 suitable for setting on another.
379 .Qq ( Li "+%m%d%H%M%Y.%S"
389 without modifying the date.
393 .Dl "date -j -f ""%a %b %d %T %Z %Y"" ""`date`"" ""+%s"""
395 can be used to parse the output from
397 and express it in Epoch time.
401 synchronizes the time on many hosts, the setting of a new time value may
402 require more than a few seconds.
406 .Ql Network time being set .
408 .Ql Communication error with timed
409 occurs when the communication
422 .%T "TSP: The Time Synchronization Protocol for UNIX 4.3BSD"
429 utility is expected to be compatible with