- 2012-11-23 → Fri 2012-11-23 00:00:00
- 12-11-23 → Fri 2012-11-23 00:00:00
- 11:12:13 → Fri 2012-11-23 11:12:13
- 11:12 → Fri 2012-11-23 11:12:00
- now → Fri 2012-11-23 18:15:22
- today → Fri 2012-11-23 00:00:00
- yesterday → Fri 2012-11-22 00:00:00
- tomorrow → Fri 2012-11-24 00:00:00
- +3h30min → Fri 2012-11-23 21:45:22
- -5s → Fri 2012-11-23 18:15:17
- 11min ago → Fri 2012-11-23 18:04:22</programlisting>
-
- <para>Note that timestamps printed by systemd will not
- be parsed correctly by systemd, as the timezone
- specification is not accepted, and printing timestamps
- is subject to locale settings for the weekday while
- parsing only accepts English weekday names.</para>
-
- <para>In some cases, systemd will display a relative
- timestamp (relative to the current time, or the time
- of invocation of the command) instead or in addition
- to an absolute timestamp as described above. A
- relative timestamp is formatted as follows:</para>
-
- <para>2 months 5 days ago</para>
-
- <para>Note that any relative timestamp will also parse
- correctly where a timestamp is expected. (see above)</para>
- </refsect1>
-
- <refsect1>
- <title>Calendar Events</title>
-
- <para>Calendar events may be used to refer to one or
- more points in time in a single expression. They form
- a superset of the absolute timestamps explained above:</para>
-
- <programlisting>Thu,Fri 2012-*-1,5 11:12:13</programlisting>
-
- <para>The above refers to 11:12:13 of the first or
- fifth day of any month of the year 2012, given that it
- is a Thursday or Friday.</para>
-
- <para>The weekday specification is optional. If
- specified, it should consist of one or more English
- language weekday names, either in the abbreviated
- (Wed) or non-abbreviated (Wednesday) form (case does
- not matter), separated by commas. Specifying two
- weekdays separated by <literal>-</literal> refers to a
- range of continuous weekdays. <literal>,</literal> and
- <literal>-</literal> may be combined freely.</para>
-
- <para>In the date and time specifications, any
- component may be specified as <literal>*</literal> in
- which case any value will match. Alternatively, each
- component can be specified as list of values separated
- by commas. Values may also be suffixed with
- <literal>/</literal> and a repetition value, which
- indicates that the value and all values plus multiples
- of the repetition value are matched.</para>
-
- <para>Either time or date specification may be
- omitted, in which case the current day and 00:00:00 is
- implied, respectively. If the second component is not
- specified <literal>:00</literal> is assumed.</para>
-
- <para>Timezone names may not be specified.</para>
-
- <para>The special expressions
- <literal>hourly</literal>, <literal>daily</literal>,
- <literal>monthly</literal> and <literal>weekly</literal>
- may be used as calendar events which refer to
- <literal>*-*-* *:00:00</literal>, <literal>*-*-*
- 00:00:00</literal>, <literal>*-*-01 00:00:00</literal> and
- <literal>Mon *-*-* 00:00:00</literal>,
- respectively.</para>
-
- <para>Examples for valid timestamps and their
- normalized form:</para>
+ 2012-11-23 → Fri 2012-11-23 00:00:00
+ 12-11-23 → Fri 2012-11-23 00:00:00
+ 11:12:13 → Fri 2012-11-23 11:12:13
+ 11:12 → Fri 2012-11-23 11:12:00
+ now → Fri 2012-11-23 18:15:22
+ today → Fri 2012-11-23 00:00:00
+ yesterday → Fri 2012-11-22 00:00:00
+ tomorrow → Fri 2012-11-24 00:00:00
+ +3h30min → Fri 2012-11-23 21:45:22
+ -5s → Fri 2012-11-23 18:15:17
+ 11min ago → Fri 2012-11-23 18:04:22
+ @1395716396 → Tue 2014-03-25 03:59:56</programlisting>
+
+ <para>Note that timestamps printed by systemd will not be parsed
+ correctly by systemd, as the timezone specification is not
+ accepted, and printing timestamps is subject to locale settings
+ for the weekday while parsing only accepts English weekday
+ names.</para>
+
+ <para>In some cases, systemd will display a relative timestamp
+ (relative to the current time, or the time of invocation of the
+ command) instead or in addition to an absolute timestamp as
+ described above. A relative timestamp is formatted as
+ follows:</para>
+
+ <para>2 months 5 days ago</para>
+
+ <para>Note that any relative timestamp will also parse correctly
+ where a timestamp is expected. (see above)</para>
+ </refsect1>
+
+ <refsect1>
+ <title>Calendar Events</title>
+
+ <para>Calendar events may be used to refer to one or more points
+ in time in a single expression. They form a superset of the
+ absolute timestamps explained above:</para>
+
+ <programlisting>Thu,Fri 2012-*-1,5 11:12:13</programlisting>
+
+ <para>The above refers to 11:12:13 of the first or fifth day of
+ any month of the year 2012, but only if that day is a Thursday or
+ Friday.</para>
+
+ <para>The weekday specification is optional. If specified, it
+ should consist of one or more English language weekday names,
+ either in the abbreviated (Wed) or non-abbreviated (Wednesday)
+ form (case does not matter), separated by commas. Specifying two
+ weekdays separated by <literal>-</literal> refers to a range of
+ continuous weekdays. <literal>,</literal> and <literal>-</literal>
+ may be combined freely.</para>
+
+ <para>In the date and time specifications, any component may be
+ specified as <literal>*</literal> in which case any value will
+ match. Alternatively, each component can be specified as a list of
+ values separated by commas. Values may also be suffixed with
+ <literal>/</literal> and a repetition value, which indicates that
+ the value and all values plus multiples of the repetition value
+ are matched.</para>
+
+ <para>Either time or date specification may be omitted, in which
+ case the current day and 00:00:00 is implied, respectively. If the
+ second component is not specified, <literal>:00</literal> is
+ assumed.</para>
+
+ <para>Timezone names may not be specified.</para>
+
+ <para>The special expressions
+ <literal>minutely</literal>,
+ <literal>hourly</literal>, <literal>daily</literal>,
+ <literal>monthly</literal>, <literal>weekly</literal>,
+ <literal>yearly</literal>,
+ <literal>quarterly</literal>,
+ <literal>semiannually</literal> may be used as
+ calendar events which refer to
+ <literal>*-*-* *:*:00</literal>,
+ <literal>*-*-* *:00:00</literal>,
+ <literal>*-*-* 00:00:00</literal>,
+ <literal>*-*-01 00:00:00</literal>,
+ <literal>Mon *-*-* 00:00:00</literal>,
+ <literal>*-01-01 00:00:00</literal>,
+ <literal>*-01,04,07,10-01 00:00:0</literal> and
+ <literal>*-01,07-01 00:00:00</literal> respectively.
+ </para>
+
+ <para>Examples for valid timestamps and their
+ normalized form:</para>