SYSTEMD.TIME(7) systemd.time SYSTEMD.TIME(7)
NAME
systemd.time - Time and date specifications
DESCRIPTION
In systemd, timestamps, time spans, and calendar events are displayed
and may be specified in closely related syntaxes.
DISPLAYING TIME SPANS
Time spans refer to time durations. On display, systemd will present
time spans as a space-separated series of time values each suffixed by
a time unit. Example:
2h 30min
All specified time values are meant to be added up. The above hence
refers to 150 minutes. Display is locale-independent, only English
names for the time units are used.
PARSING TIME SPANS
When parsing, systemd will accept the same time span syntax. Separating
spaces may be omitted. The following time units are understood:
o usec, us, <micro>s
o msec, ms
o seconds, second, sec, s
o minutes, minute, min, m
o hours, hour, hr, h
o days, day, d
o weeks, week, w
o months, month, M (defined as 30.44 days)
o years, year, y (defined as 365.25 days)
If no time unit is specified, generally seconds are assumed, but some
exceptions exist and are marked as such. In a few cases "ns", "nsec" is
accepted too, where the granularity of the time span permits this.
Parsing is generally locale-independent, non-English names for the time
units are not accepted.
Examples for valid time span specifications:
2 h
2hours
48hr
1y 12month
55s500ms
300ms20s 5day
One can use the timespan command of systemd-analyze(1) to normalise a
textual time span for testing and validation purposes.
Internally, systemd generally operates with microsecond time
granularity, while the default time unit in user-configurable time
spans is usually seconds (see above). This disparity becomes visible
when comparing the same settings in the (high-level) unit file syntax
with the matching (more low-level) D-Bus properties (which are what
systemctl(1)'s show command displays). The former typically are
suffixed with "...Sec" to indicate the default unit of seconds, the
latter are typically suffixed with "...USec" to indicate the underlying
low-level time unit, even if they both encapsulate the very same
settings.
DISPLAYING TIMESTAMPS
Timestamps refer to specific, unique points in time. On display,
systemd will format these in the local timezone as follows:
Fri 2012-11-23 23:02:15 CET
The weekday is printed in the abbreviated English language form. The
formatting is locale-independent.
In some cases timestamps are shown in the UTC timezone instead of the
local timezone, which is indicated via the "UTC" timezone specifier in
the output.
In some cases timestamps are shown with microsecond granularity. In
this case the sub-second remainder is separated by a full stop from the
seconds component.
PARSING TIMESTAMPS
When parsing, systemd will accept a similar syntax, but expects no
timezone specification, unless it is given as the literal string "UTC"
(for the UTC timezone), or is specified to be the locally configured
timezone, or the timezone name in the IANA timezone database format.
The complete list of timezones supported on your system can be obtained
using the "timedatectl list-timezones" (see timedatectl(1)). Using IANA
format is recommended over local timezone names, as less prone to
errors (e.g. with local timezone it's possible to specify daylight
saving time in winter, even though that is not correct). The weekday
specification is optional, but when the weekday is specified, it must
either be in the abbreviated ("Wed") or non-abbreviated ("Wednesday")
English language form (case does not matter), and is not subject to the
locale choice of the user. Either the date, or the time part may be
omitted, in which case the current date or 00:00:00, respectively, is
assumed. The seconds component of the time may also be omitted, in
which case ":00" is assumed. Year numbers may be specified in full or
may be abbreviated (omitting the century).
A timestamp is considered invalid if a weekday is specified and the
date does not match the specified day of the week.
When parsing, systemd will also accept a few special placeholders
instead of timestamps: "now" may be used to refer to the current time
(or of the invocation of the command that is currently executed).
"today", "yesterday", and "tomorrow" refer to 00:00:00 of the current
day, the day before, or the next day, respectively.
When parsing, systemd will also accept relative time specifications. A
time span (see above) that is prefixed with "+" is evaluated to the
current time plus the specified time span. Correspondingly, a time span
that is prefixed with "-" is evaluated to the current time minus the
specified time span. Instead of prefixing the time span with "+" or
"-", it may also be suffixed with a space and the word "left" or "ago".
Finally, a timespan prefixed with "@" is evaluated relative to the UNIX
time epoch 1st Jan, 1970, 00:00.
Examples for valid timestamps and their normalized form (assuming the
current time was 2012-11-23 18:15:22 and the timezone was UTC+8, for
example "TZ=:Asia/Shanghai"):
Fri 2012-11-23 11:12:13 Fri 2012-11-23 11:12:13
2012-11-23 11:12:13 Fri 2012-11-23 11:12:13
2012-11-23 11:12:13 UTC Fri 2012-11-23 19:12:13
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
today UTC Fri 2012-11-23 16:00:00
yesterday Fri 2012-11-22 00:00:00
tomorrow Fri 2012-11-24 00:00:00
tomorrow Pacific/Auckland Thu 2012-11-23 19: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
Note that timestamps displayed by remote systems with a non-matching
timezone are usually not parsable locally, as the timezone component is
not u'
SYSTEMD.TIME(7) systemd.time SYSTEMD.TIME(7)
NAME
systemd.time - Time and date specifications
DESCRIPTION
In systemd, timestamps, time spans, and calendar events are displayed
and may be specified in closely related syntaxes.
DISPLAYING TIME SPANS
Time spans refer to time durations. On display, systemd will present
time spans as a space-separated series of time values each suffixed by
a time unit. Example:
2h 30min
All specified time values are meant to be added up. The above hence
refers to 150 minutes. Display is locale-independent, only English
names for the time units are used.
PARSING TIME SPANS
When parsing, systemd will accept the same time span syntax. Separating
spaces may be omitted. The following time units are understood:
o usec, us, <micro>s
o msec, ms
o seconds, second, sec, s
o minutes, minute, min, m
o hours, hour, hr, h
o days, day, d
o weeks, week, w
o months, month, M (defined as 30.44 days)
o years, year, y (defined as 365.25 days)
If no time unit is specified, generally seconds are assumed, but some
exceptions exist and are marked as such. In a few cases "ns", "nsec" is
accepted too, where the granularity of the time span permits this.
Parsing is generally locale-independent, non-English names for the time
units are not accepted.
Examples for valid time span specifications:
2 h
2hours
48hr
1y 12month
55s500ms
300ms20s 5day
One can use the timespan command of systemd-analyze(1) to normalise a
textual time span for testing and validation purposes.
Internally, systemd generally operates with microsecond time
granularity, while the default time unit in user-configurable time
spans is usually seconds (see above). This disparity becomes visible
when comparing the same settings in the (high-level) unit file syntax
with the matching (more low-level) D-Bus properties (which are what
systemctl(1)'s show command displays). The former typically are
suffixed with "...Sec" to indicate the default unit of seconds, the
latter are typically suffixed with "...USec" to indicate the underlying
low-level time unit, even if they both encapsulate the very same
settings.
DISPLAYING TIMESTAMPS
Timestamps refer to specific, unique points in time. On display,
systemd will format these in the local timezone as follows:
Fri 2012-11-23 23:02:15 CET
The weekday is printed in the abbreviated English language form. The
formatting is locale-independent.
In some cases timestamps are shown in the UTC timezone instead of the
local timezone, which is indicated via the "UTC" timezone specifier in
the output.
In some cases timestamps are shown with microsecond granularity. In
this case the sub-second remainder is separated by a full stop from the
seconds component.
PARSING TIMESTAMPS
When parsing, systemd will accept a similar syntax, but expects no
timezone specification, unless it is given as the literal string "UTC"
(for the UTC timezone), or is specified to be the locally configured
timezone, or the timezone name in the IANA timezone database format.
The complete list of timezones supported on your system can be obtained
using the "timedatectl list-timezones" (see timedatectl(1)). Using IANA
format is recommended over local timezone names, as less prone to
errors (e.g. with local timezone it's possible to specify daylight
saving time in winter, even though that is not correct). The weekday
specification is optional, but when the weekday is specified, it must
either be in the abbreviated ("Wed") or non-abbreviated ("Wednesday")
English language form (case does not matter), and is not subject to the
locale choice of the user. Either the date, or the time part may be
omitted, in which case the current date or 00:00:00, respectively, is
assumed. The seconds component of the time may also be omitted, in
which case ":00" is assumed. Year numbers may be specified in full or
may be abbreviated (omitting the century).
A timestamp is considered invalid if a weekday is specified and the
date does not match the specified day of the week.
When parsing, systemd will als
systemd 252 SYSTEMD.TIME(7)
Czas wygenerowania: 0.00024 sek.
Created with the man page lookup class by Andrew Collington.
Based on a C man page viewer by Vadim Pavlov
Unicode soft-hyphen fix (as used by RedHat) by Dan Edwards
Some optimisations by Eli Argon
Caching idea and code contribution by James Richardson
Copyright © 2003-2025 Linux.pl
Hosted by Hosting Linux.pl