1 <html><head><meta http-equiv=
"Content-Type" content=
"text/html; charset=UTF-8"><title>systemd.time
</title><meta name=
"generator" content=
"DocBook XSL Stylesheets V1.78.1"></head><body bgcolor=
"white" text=
"black" link=
"#0000FF" vlink=
"#840084" alink=
"#0000FF"><style>
11 background-color: #c60f0f;
15 h1:hover
> a.headerlink, h2:hover
> a.headerlink, h3:hover
> a.headerlink, dt:hover
> a.headerlink {
18 </style><a href=
"index.html">Index
</a>·
19 <a href=
"systemd.directives.html">Directives
</a>·
20 <a href=
"../python-systemd/index.html">Python
</a>·
21 <a href=
"../libudev/index.html">libudev
</a>·
22 <a href=
"../libudev/index.html">gudev
</a><span style=
"float:right">systemd
204</span><hr><div class=
"refentry"><a name=
"systemd.time"></a><div class=
"titlepage"></div><div class=
"refnamediv"><h2>Name
</h2><p>systemd.time — Time and date specifications
</p></div><div class=
"refsect1"><a name=
"idm259769968128"></a><h2 id=
"Description">Description
<a class=
"headerlink" title=
"Permalink to this headline" href=
"#Description">¶
</a></h2><p>In systemd timestamps, timespans, and calendar
23 events are displayed and may be specified in closely
24 related syntaxes.
</p></div><div class=
"refsect1"><a name=
"idm259769966784"></a><h2 id=
"Displaying Timespans">Displaying Timespans
<a class=
"headerlink" title=
"Permalink to this headline" href=
"#Displaying%20Timespans">¶
</a></h2><p>Timespans refer to time durations. On display
25 systemd will present timespans as a space separated
26 series of time values each suffixed by a time
27 unit.
</p><pre class=
"programlisting">2h
30min
</pre><p>All specified time values are meant to be added
28 up. The above hence refers to
150 minutes.
</p></div><div class=
"refsect1"><a name=
"idm259769964304"></a><h2 id=
"Parsing Timespans">Parsing Timespans
<a class=
"headerlink" title=
"Permalink to this headline" href=
"#Parsing%20Timespans">¶
</a></h2><p>When parsing systemd will accept the same
29 timespan syntax. Separating spaces may be omitted. The
30 following time units are understood:
</p><div class=
"itemizedlist"><ul class=
"itemizedlist" style=
"list-style-type: disc; "><li class=
"listitem"><p>usec, us
</p></li><li class=
"listitem"><p>msec, ms
</p></li><li class=
"listitem"><p>seconds, second, sec, s
</p></li><li class=
"listitem"><p>minutes, minute, min, m
</p></li><li class=
"listitem"><p>hours, hour, hr, h
</p></li><li class=
"listitem"><p>days, day, d
</p></li><li class=
"listitem"><p>weeks, week, w
</p></li><li class=
"listitem"><p>months, month
</p></li><li class=
"listitem"><p>years, year, y
</p></li></ul></div><p>If no time unit is specified, generally seconds
31 are assumed, but some exceptions exist and are marked
32 as such. In a few cases
<code class=
"literal">ns
</code>,
33 <code class=
"literal">nsec
</code> is accepted too, where the
34 granularity of the timespan allows for this.
</p><p>Examples for valid timespan specifications:
</p><pre class=
"programlisting">2 h
39 300ms20s
5day
</pre></div><div class=
"refsect1"><a name=
"idm259769954688"></a><h2 id=
"Displaying Timestamps">Displaying Timestamps
<a class=
"headerlink" title=
"Permalink to this headline" href=
"#Displaying%20Timestamps">¶
</a></h2><p>Timestamps refer to specific, unique points in
40 time. On display systemd will format these in the
41 local timezone as follows:
</p><pre class=
"programlisting">Fri
2012-
11-
23 23:
02:
15 CET
</pre><p>The week day is printed according to the locale
42 choice of the user.
</p></div><div class=
"refsect1"><a name=
"idm259769952240"></a><h2 id=
"Parsing Timestamps">Parsing Timestamps
<a class=
"headerlink" title=
"Permalink to this headline" href=
"#Parsing%20Timestamps">¶
</a></h2><p>When parsing systemd will accept a similar
43 timestamp syntax, but excluding any timezone
44 specification (this limitation might be removed
45 eventually). The week day specification is optional,
46 but when the week day is specified it must either be
47 in the abbreviated (
<code class=
"literal">Wed
</code>) or
48 non-abbreviated (
<code class=
"literal">Wednesday
</code>) english
49 language form (case doesn't matter), and is not
50 subject to the locale choice of the user. Either the
51 date, or the time part may be omitted, in which case
52 the current date or
00:
00:
00, resp., is assumed. The
53 seconds component of the time may also be omitted, in
54 which case
":00" is assumed. Year numbers may be
55 specified in full or may be abbreviated (omitting the
56 century).
</p><p>A timestamp is considered invalid if a week day
57 is specified and the date does not actually match the
58 specified day of the week.
</p><p>When parsing systemd will also accept a few
59 special placeholders instead of timestamps:
60 <code class=
"literal">now
</code> may be used to refer to the
61 current time (or of the invocation of the command
62 that is currently executed).
<code class=
"literal">today
</code>,
63 <code class=
"literal">yesterday
</code>,
64 <code class=
"literal">tomorrow
</code> refer to
00:
00:
00 of the
65 current day, the day before or the next day,
66 respectively.
</p><p>When parsing systemd will also accept relative
67 time specifications. A timespan (see above) that is
68 prefixed with
<code class=
"literal">+
</code> is evaluated to the
69 current time plus the specified
70 timespan. Correspondingly a timespan that is prefix
71 with
<code class=
"literal">-
</code> is evaluated to the current
72 time minus the specified timespan. Instead of
73 prefixing the timespan with
<code class=
"literal">-
</code> it
74 may also be suffixed with a space and the word
75 <code class=
"literal">ago
</code>.
</p><p>Examples for valid timestamps and their
76 normalized form (assuming the current time was
77 2012-
11-
23 18:
15:
22):
</p><pre class=
"programlisting">Fri
2012-
11-
23 11:
12:
13 → Fri
2012-
11-
23 11:
12:
13
78 2012-
11-
23 11:
12:
13 → Fri
2012-
11-
23 11:
12:
13
79 2012-
11-
23 → Fri
2012-
11-
23 00:
00:
00
80 12-
11-
23 → Fri
2012-
11-
23 00:
00:
00
81 11:
12:
13 → Fri
2012-
11-
23 11:
12:
13
82 11:
12 → Fri
2012-
11-
23 11:
12:
00
83 now → Fri
2012-
11-
23 18:
15:
22
84 today → Fri
2012-
11-
23 00:
00:
00
85 yesterday → Fri
2012-
11-
22 00:
00:
00
86 tomorrow → Fri
2012-
11-
24 00:
00:
00
87 +
3h30min → Fri
2012-
11-
23 21:
45:
22
88 -
5s → Fri
2012-
11-
23 18:
15:
17
89 11min ago → Fri
2012-
11-
23 18:
04:
22</pre><p>Note that timestamps printed by systemd will not
90 be parsed correctly by systemd, as the timezone
91 specification is not accepted, and printing timestamps
92 is subject to locale settings for the week day while
93 parsing only accepts english week day names.
</p><p>In some cases systemd will display a relative
94 timestamp (relative to the current time, or the time
95 of invocation of the command) instead or in addition
96 to an absolute timestamp as described above. A
97 relative timestamp is formatted as follows:
</p><p>2 months
5 days ago
</p><p>Note that any relative timestamp will also parse
98 correctly where a timestamp is expected. (see above)
</p></div><div class=
"refsect1"><a name=
"idm259773833232"></a><h2 id=
"Calendar Events">Calendar Events
<a class=
"headerlink" title=
"Permalink to this headline" href=
"#Calendar%20Events">¶
</a></h2><p>Calendar events may be used to refer to one or
99 more points in time in a single expression. They form
100 a superset of the absolute timestamps explained above:
</p><pre class=
"programlisting">Thu,Fri
2012-*-
1,
5 11:
12:
13</pre><p>The above refers to
11:
12:
13 of the first or
101 fifth day of any month of the year
2012, given that it
102 is a thursday or friday.
</p><p>The weekday specification is optional. If
103 specified it should consist of one or more english
104 language week day names, either in the abbreviated
105 (Wed) or non-abbreviated (Wednesday) form (case does
106 not matter), separated by commas. Specifying two week
107 days separated by
"-" refers to a range of continuous
108 week days.
"," and
"-" may be combined freely.
</p><p>In the date and time specifications any
109 component may be specified as
"*" in which case any
110 value will match. Alternatively, each component can be
111 specified as list of values separated by
112 commas. Values may also be suffixed with
"/" and a
113 repetition value, which indicates that the value and
114 all values plus multiples of the repetition value are
115 matched.
</p><p>Either time or date specification may be
116 omitted, in which case the current day and
00:
00:
00 is
117 implied, respectively. If the second component is not
118 specified
":00" is assumed.
</p><p>Timezone names may not be specified.
</p><p>The special expressions
119 <code class=
"literal">hourly
</code>,
<code class=
"literal">daily
</code>,
120 <code class=
"literal">monthly
</code> and
<code class=
"literal">weekly
</code>
121 may be used as calendar events which refer to
122 <code class=
"literal">*-*-* *:
00:
00</code>,
<code class=
"literal">*-*-*
123 00:
00:
00</code>,
<code class=
"literal">*-*-
01 00:
00:
00</code> and
124 <code class=
"literal">Mon *-*-*
00:
00:
00</code>,
125 respectively.
</p><p>Examples for valid timestamps and their
126 normalized form:
</p><pre class=
"programlisting"> Sat,Thu,Mon-Wed,Sat-Sun → Mon-Thu,Sat,Sun *-*-*
00:
00:
00
127 Mon,Sun
12-*-*
2,
1:
23 → Mon,Sun
2012-*-*
01,
02:
23:
00
128 Wed *-
1 → Wed *-*-
01 00:
00:
00
129 Wed-Wed,Wed *-
1 → Wed *-*-
01 00:
00:
00
130 Wed,
17:
48 → Wed *-*-*
17:
48:
00
131 Wed-Sat,Tue
12-
10-
15 1:
2:
3 → Tue-Sat
2012-
10-
15 01:
02:
03
132 *-*-
7 0:
0:
0 → *-*-
07 00:
00:
00
133 10-
15 → *-
10-
15 00:
00:
00
134 monday *-
12-*
17:
00 → Mon *-
12-*
17:
00:
00
135 Mon,Fri *-*-
3,
1,
2 *:
30:
45 → Mon,Fri *-*-
01,
02,
03 *:
30:
45
136 12,
14,
13,
12:
20,
10,
30 → *-*-*
12,
13,
14:
10,
20,
30:
00
137 mon,fri *-
1/
2-
1,
3 *:
30:
45 → Mon,Fri *-
01/
2-
01,
03 *:
30:
45
138 03-
05 08:
05:
40 → *-
03-
05 08:
05:
40
139 08:
05:
40 → *-*-*
08:
05:
40
140 05:
40 → *-*-*
05:
40:
00
141 Sat,Sun
12-
05 08:
05:
40 → Sat,Sun *-
12-
05 08:
05:
40
142 Sat,Sun
08:
05:
40 → Sat,Sun *-*-*
08:
05:
40
143 2003-
03-
05 05:
40 →
2003-
03-
05 05:
40:
00
144 2003-
03-
05 →
2003-
03-
05 00:
00:
00
145 03-
05 → *-
03-
05 00:
00:
00
146 hourly → *-*-* *:
00:
00
147 daily → *-*-*
00:
00:
00
148 monthly → *-*-
01 00:
00:
00
149 weekly → Mon *-*-*
00:
00:
00
150 *:
2/
3 → *-*-* *:
02/
3:
00</pre><p>Calendar events are used by timer units, see
151 <a href=
"systemd.timer.html"><span class=
"citerefentry"><span class=
"refentrytitle">systemd.timer
</span>(
5)
</span></a>
152 for details.
</p></div><div class=
"refsect1"><a name=
"idm259773906032"></a><h2 id=
"See Also">See Also
<a class=
"headerlink" title=
"Permalink to this headline" href=
"#See%20Also">¶
</a></h2><p>
153 <a href=
"systemd.html"><span class=
"citerefentry"><span class=
"refentrytitle">systemd
</span>(
1)
</span></a>,
154 <a href=
"journalctl.html"><span class=
"citerefentry"><span class=
"refentrytitle">journalctl
</span>(
1)
</span></a>,
155 <a href=
"systemd.timer.html"><span class=
"citerefentry"><span class=
"refentrytitle">systemd.timer
</span>(
5)
</span></a>,
156 <a href=
"systemd.unit.html"><span class=
"citerefentry"><span class=
"refentrytitle">systemd.unit
</span>(
5)
</span></a>,
157 <a href=
"systemd.directives.html"><span class=
"citerefentry"><span class=
"refentrytitle">systemd.directives
</span>(
7)
</span></a>
158 </p></div></div></body></html>
projects / systemd.git / blob