<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>systemd on allddd</title><link>https://www.allddd.onl/tags/systemd/</link><description>Recent content in systemd on allddd</description><generator>Hugo</generator><language>en</language><lastBuildDate>Tue, 17 Nov 2026 19:59:55 +0000</lastBuildDate><atom:link href="https://www.allddd.onl/tags/systemd/index.xml" rel="self" type="application/rss+xml"/><item><title>What systemd.time(7) leaves out</title><link>https://www.allddd.onl/blog/what-systemd-time-leaves-out/</link><pubDate>Tue, 17 Nov 2026 19:59:55 +0000</pubDate><guid>https://www.allddd.onl/blog/what-systemd-time-leaves-out/</guid><description>&lt;p&gt;Timers, &lt;code&gt;journalctl --since&lt;/code&gt; and many unit settings use the same time syntax, and its only documentation is &lt;a href="https://www.freedesktop.org/software/systemd/man/latest/systemd.time.html"&gt;systemd.time(7)&lt;/a&gt;. Writing a &lt;a href="https://gitlab.com/allddd/go-systemd-time"&gt;Go implementation&lt;/a&gt; of it for a separate project showed that the man page leaves out a lot of cases and isn’t always right, so the closest thing to a spec is the C code, which (luckily) has comments for many of the odd parts.&lt;/p&gt;
&lt;p&gt;The output below comes from systemd 262, with &lt;code&gt;faketime -f '2027-01-01 00:00:00'&lt;/code&gt; from &lt;a href="https://github.com/wolfcw/libfaketime"&gt;libfaketime&lt;/a&gt; in front of every &lt;code&gt;systemd-analyze&lt;/code&gt;.&lt;/p&gt;</description><content:encoded><![CDATA[<p>Timers, <code>journalctl --since</code> and many unit settings use the same time syntax, and its only documentation is <a href="https://www.freedesktop.org/software/systemd/man/latest/systemd.time.html">systemd.time(7)</a>. Writing a <a href="https://gitlab.com/allddd/go-systemd-time">Go implementation</a> of it for a separate project showed that the man page leaves out a lot of cases and isn’t always right, so the closest thing to a spec is the C code, which (luckily) has comments for many of the odd parts.</p>
<p>The output below comes from systemd 262, with <code>faketime -f '2027-01-01 00:00:00'</code> from <a href="https://github.com/wolfcw/libfaketime">libfaketime</a> in front of every <code>systemd-analyze</code>.</p>
<h2 id="time-spans">Time spans</h2>
<p>A time span is a list of numbers and units, which are all added up, so <code>2h 30min</code> is 150 minutes. <code>systemd-analyze timespan</code> prints the result in microseconds and the way systemd displays it.</p>
<h3 id="months">Months</h3>
<p>The man page says a month is 30.44 days, but systemd uses a year divided by 12, which is 30.4375 days.</p>
<pre tabindex="0"><code>$ systemd-analyze timespan 1M 30.44d
Original: 1M
      μs: 2629800000000
   Human: 1month

Original: 30.44d
      μs: 2630016000000
   Human: 1month 3min 36s
</code></pre><p>A parser that follows the man page is off by 3 minutes and 36 seconds per month.</p>
<h3 id="case-sensitivity">Case sensitivity</h3>
<p>Units are case-sensitive, and <code>M</code> is the only one in uppercase. <code>m</code> is a minute and <code>M</code> is a month, while <code>H</code>, <code>D</code> or <code>Min</code> don’t work at all.</p>
<pre tabindex="0"><code>$ systemd-analyze timespan 1m 1H
Original: 1m
      μs: 60000000
   Human: 1min

Failed to parse time span &#39;1H&#39;: Invalid argument
</code></pre><h3 id="plurals">Plurals</h3>
<p>Units are matched by prefix against a fixed list, and anything left after the match is read as the next number. <code>days</code> is in the list, but <code>hrs</code>, <code>mins</code> and <code>secs</code> aren’t, so <code>hr</code>, <code>min</code> and <code>sec</code> match and the <code>s</code> left over fails.</p>
<pre tabindex="0"><code>$ systemd-analyze timespan 1days 1hrs
Original: 1days
      μs: 86400000000
   Human: 1d

Failed to parse time span &#39;1hrs&#39;: Invalid argument
</code></pre><h3 id="bare-numbers">Bare numbers</h3>
<p>A number without a unit is seconds in most places, even at the end of a longer span. <code>1hr30</code> looks like an hour and a half, but it’s an hour and 30 seconds.</p>
<pre tabindex="0"><code>$ systemd-analyze timespan 1hr30
Original: 1hr30
      μs: 3630000000
   Human: 1h 30s
</code></pre><h3 id="signs-and-dots">Signs and dots</h3>
<p>Each number is read with <code>strtoll()</code>, which accepts a leading <code>+</code>, so <code>5s+5s</code> is 10 seconds. A second decimal point right after a number fails, but a space/unit in between starts a new number.</p>
<pre tabindex="0"><code>$ systemd-analyze timespan 5s+5s &#39;12.34 .56&#39; 12.34.56
Original: 5s+5s
      μs: 10000000
   Human: 10s

Original: 12.34 .56
      μs: 12900000
   Human: 12.900000s

Failed to parse time span &#39;12.34.56&#39;: Invalid argument
</code></pre><h3 id="fractions">Fractions</h3>
<p>Fractions are cut off below a microsecond instead of rounded, and that happens for <a href="https://github.com/systemd/systemd/blob/v262/src/basic/time-util.c#L1254">each number separately</a>, so <code>0.5us 0.5us</code> is 0.</p>
<pre tabindex="0"><code>$ systemd-analyze timespan &#39;0.5us 0.5us&#39; 1.9999999s
Original: 0.5us 0.5us
      μs: 0
   Human: 0

Original: 1.9999999s
      μs: 1999999
   Human: 1.999999s
</code></pre><h3 id="infinity">Infinity</h3>
<p><code>infinity</code> is a valid time span too, even though the man page doesn’t list it. It’s the largest value systemd can store, and settings like <code>TimeoutStopSec=</code> use it to turn the timeout off.</p>
<pre tabindex="0"><code>$ systemd-analyze timespan infinity
Original: infinity
      μs: 18446744073709551615
   Human: infinity
</code></pre><h2 id="timestamps">Timestamps</h2>
<p>A timestamp is a weekday, a date, a time and a timezone, most of which can be left out, or one of a few special forms like <code>now</code>, <code>+5h</code> or <code>@1234567890</code>. <code>systemd-analyze timestamp</code> prints it in the local timezone and as seconds since the epoch.</p>
<h3 id="two-digit-years">Two-digit years</h3>
<p>Years can have two digits, which the man page shows in an example but doesn’t explain. <code>00</code> to <code>68</code> become 2000 to 2068, and <code>69</code> to <code>99</code> become 1969 to 1999.</p>
<pre tabindex="0"><code>$ TZ=UTC systemd-analyze timestamp 68-01-01 69-01-01 70-01-01
  Original form: 68-01-01
Normalized form: Sun 2068-01-01 00:00:00 UTC
   UNIX seconds: @3092601600
       From now: 40 years 11 months left

Failed to parse &#34;69-01-01&#34;: Numerical result out of range
Hint: this expression is a valid calendar specification. Use &#39;systemd-analyze calendar &#34;69-01-01&#34;&#39; instead?

  Original form: 70-01-01
Normalized form: -
   UNIX seconds: @0
       From now: -
</code></pre><p>Timestamps can’t go below the epoch, so <code>69-01-01</code> (1969) is out of range. <code>70-01-01</code> is exactly the epoch, which is 0, and systemd prints a timestamp of 0 as <code>-</code>. With a 64-bit <code>time_t</code>, the upper limit is 9999-12-30 23:59:59 UTC, a day before the year 9999 ends, so that no timezone can push it into a five-digit year (<a href="https://github.com/systemd/systemd/blob/v262/src/basic/time-util.h#L256">source</a>).</p>
<p>The conversion itself comes from <code>%y</code> in <code>strptime()</code>, not from systemd. Calendar events have <a href="https://github.com/systemd/systemd/blob/v262/src/shared/calendarspec.c#L126">their own</a>, where <code>00</code> to <code>69</code> become 2000 to 2069 and <code>70</code> to <code>99</code> become 1970 to 1999, so <code>69-01-01</code> is a valid event (and the reason for the hint above).</p>
<pre tabindex="0"><code>$ TZ=UTC systemd-analyze calendar 69-01-01 70-01-01
  Original form: 69-01-01
Normalized form: 2069-01-01 00:00:00
    Next elapse: Tue 2069-01-01 00:00:00 UTC
       From now: 42 years 0 months left

  Original form: 70-01-01
Normalized form: 1970-01-01 00:00:00
    Next elapse: never
</code></pre><p>The <code>T</code> between date and time (as in RFC 3339) only works with four-digit years, which the man page doesn’t mention. With a <code>T</code>, the year is taken as written, so <code>09</code> is the year 9 and out of range.</p>
<pre tabindex="0"><code>$ TZ=UTC systemd-analyze timestamp 2009-11-10T18:15:22 09-11-10T18:15:22
  Original form: 2009-11-10T18:15:22
Normalized form: Tue 2009-11-10 18:15:22 UTC
   UNIX seconds: @1257876922
       From now: 17 years 1 month ago

Failed to parse &#34;09-11-10T18:15:22&#34;: Numerical result out of range
</code></pre><h3 id="timezones">Timezones</h3>
<p>The man page lists <code>UTC</code>, <code>Z</code>, offsets and names from the IANA database. Abbreviations only work when the database has a zone by that name or when they belong to the local timezone, so in UTC <code>CET</code> works and <code>PST</code> doesn’t.</p>
<pre tabindex="0"><code>$ TZ=UTC systemd-analyze timestamp &#39;2009-11-10 18:15:22 CET&#39; &#39;2009-11-10 18:15:22 PST&#39;
  Original form: 2009-11-10 18:15:22 CET
Normalized form: Tue 2009-11-10 17:15:22 UTC
   UNIX seconds: @1257873322
       From now: 17 years 1 month ago

Failed to parse &#34;2009-11-10 18:15:22 PST&#34;: Invalid argument
</code></pre><p><code>timedatectl list-timezones</code> shows which names are in the database (e.g., <code>EST</code> is one, but US west coast time is <code>America/Los_Angeles</code>, <code>US/Pacific</code> or <code>PST8PDT</code>). With <code>TZ=America/Los_Angeles</code>, <code>PST</code> and <code>PDT</code> work.</p>
<p>A local abbreviation also decides whether daylight saving time applies, no matter the date. In New York, <code>EDT</code> in December is 4 hours behind UTC, an hour off from <code>EST</code>.</p>
<pre tabindex="0"><code>$ TZ=America/New_York systemd-analyze timestamp &#39;2009-12-10 18:15:22 EST&#39; &#39;2009-12-10 18:15:22 EDT&#39;
  Original form: 2009-12-10 18:15:22 EST
Normalized form: Thu 2009-12-10 18:15:22 EST
       (in UTC): Thu 2009-12-10 23:15:22 UTC
   UNIX seconds: @1260486922
       From now: 17 years 0 months ago

  Original form: 2009-12-10 18:15:22 EDT
Normalized form: Thu 2009-12-10 17:15:22 EST
       (in UTC): Thu 2009-12-10 22:15:22 UTC
   UNIX seconds: @1260483322
       From now: 17 years 0 months ago
</code></pre><h3 id="weekdays">Weekdays</h3>
<p>Unlike units, weekday names don’t care about case, but <code>now</code>, <code>today</code>, <code>yesterday</code> and <code>tomorrow</code> only work in lowercase. A weekday in front of a date also has to match it.</p>
<pre tabindex="0"><code>$ TZ=UTC systemd-analyze timestamp &#39;Wed 2009-11-10&#39; &#39;TUESDAY 2009-11-10&#39; Today
Failed to parse &#34;Wed 2009-11-10&#34;: Invalid argument
Hint: this expression is a valid calendar specification. Use &#39;systemd-analyze calendar &#34;Wed 2009-11-10&#34;&#39; instead?

  Original form: TUESDAY 2009-11-10
Normalized form: Tue 2009-11-10 00:00:00 UTC
   UNIX seconds: @1257811200
       From now: 17 years 1 month ago

Failed to parse &#34;Today&#34;: Invalid argument
</code></pre><p>2009-11-10 was a Tuesday, so <code>Wed 2009-11-10</code> is rejected. The hint doesn’t help much, since as a calendar event it <a href="#limits">never elapses</a> either.</p>
<h3 id="unix-time">Unix time</h3>
<p><code>@</code> isn’t limited to an integer. Everything after it is <a href="https://github.com/systemd/systemd/blob/v262/src/basic/time-util.c#L830">parsed as a time span</a>, so <code>@1h</code> is an hour after the epoch, and even <code>@infinity</code> works.</p>
<pre tabindex="0"><code>$ TZ=UTC systemd-analyze timestamp @1h @infinity
  Original form: @1h
Normalized form: Thu 1970-01-01 01:00:00 UTC
   UNIX seconds: @3600
       From now: 56 years 11 months ago

  Original form: @infinity
Normalized form: -
   UNIX seconds: @18446744073709.551615
       From now: -
</code></pre><h3 id="syslog-format">Syslog format</h3>
<p>The format <code>journalctl</code> prints by default, e.g., <code>Dec 31 23:00:00</code>, <a href="https://github.com/systemd/systemd/blob/v262/src/basic/time-util.c#L948">is accepted</a>, even though the man page doesn’t list it. It has no year, so it’s always the current one, and <code>journalctl --since 'Dec 31 23:00:00'</code> on New Year’s Day finds nothing from the night before.</p>
<pre tabindex="0"><code>$ TZ=UTC systemd-analyze timestamp &#39;Dec 31 23:00:00&#39;
  Original form: Dec 31 23:00:00
Normalized form: Fri 2027-12-31 23:00:00 UTC
   UNIX seconds: @1830294000
       From now: 11 months 30 days left
</code></pre><h3 id="spaces">Spaces</h3>
<p>Leading and doubled spaces are fine, but a trailing one breaks the whole timestamp, since the <a href="https://github.com/systemd/systemd/blob/v262/src/basic/time-util.c#L1088">last space</a> is where the timezone is expected to start.</p>
<pre tabindex="0"><code>$ TZ=UTC systemd-analyze timestamp &#39; 2027-01-01  12:00&#39; &#39;2027-01-01 12:00 &#39;
  Original form:  2027-01-01  12:00
Normalized form: Fri 2027-01-01 12:00:00 UTC
   UNIX seconds: @1798804800
       From now: 12h left

Failed to parse &#34;2027-01-01 12:00 &#34;: Invalid argument
</code></pre><h2 id="calendar-events">Calendar events</h2>
<p>A calendar event matches any number of points in time instead of a single one, and it’s what <code>OnCalendar=</code> takes. <code>systemd-analyze calendar</code> shows when it elapses next, and <code>--iterations</code> shows the ones after that.</p>
<h3 id="shorthands">Shorthands</h3>
<p>Shorthands like <code>daily</code> or <code>weekly</code> don’t care about case, unlike <code>today</code>, and the misspelled <code>anually</code> works too, for <a href="https://github.com/systemd/systemd/blob/v262/src/shared/calendarspec.c#L983">backwards compatibility</a>.</p>
<pre tabindex="0"><code>$ TZ=UTC systemd-analyze calendar DAILY anually
  Original form: DAILY
Normalized form: *-*-* 00:00:00
    Next elapse: Sat 2027-01-02 00:00:00 UTC
       From now: 24h left

  Original form: anually
Normalized form: *-01-01 00:00:00
    Next elapse: Sat 2028-01-01 00:00:00 UTC
       From now: 11 months 30 days left
</code></pre><h3 id="repetitions">Repetitions</h3>
<p>A repetition without an end has to <a href="https://github.com/systemd/systemd/blob/v262/src/shared/calendarspec.c#L202">match at least twice</a>, so <code>*:50/15</code> fails even though <code>*:50</code> works. With an end, the same problem is fixed quietly, and <code>*:10..15/10</code> becomes <code>*:10</code>.</p>
<pre tabindex="0"><code>$ TZ=UTC systemd-analyze calendar &#39;*:10..15/10&#39; &#39;*:50/15&#39;
  Original form: *:10..15/10
Normalized form: *-*-* *:10:00
    Next elapse: Fri 2027-01-01 00:10:00 UTC
       From now: 10min left

Failed to parse calendar specification &#39;*:50/15&#39;: Invalid argument
</code></pre><h3 id="last-days">Last days</h3>
<p><code>~</code> instead of <code>-</code> in front of the day counts from the end of the month, so <code>*-*~1</code> is the last day of every month. Ranges work there, but only from the lower number to the higher one, even though they count backwards, so <code>~1..3</code> works and <code>~3..1</code> doesn’t. <code>~</code> also only goes up to 28.</p>
<pre tabindex="0"><code>$ TZ=UTC systemd-analyze calendar --iterations=3 &#39;*-*~1..3&#39; &#39;*-*~3..1&#39; &#39;*-*~29&#39;
  Original form: *-*~1..3
Normalized form: *-*~01..03 00:00:00
    Next elapse: Fri 2027-01-29 00:00:00 UTC
       From now: 4 weeks 0 days left
   Iteration #2: Sat 2027-01-30 00:00:00 UTC
       From now: 4 weeks 1 day left
   Iteration #3: Sun 2027-01-31 00:00:00 UTC
       From now: 4 weeks 2 days left

Failed to parse calendar specification &#39;*-*~3..1&#39;: Invalid argument

Failed to parse calendar specification &#39;*-*~29&#39;: Invalid argument
</code></pre><p>Combined with a weekday and a repetition, it can also match the last Monday of a month. <code>~07/1</code> is every day of the last 7, and only one of them can be a Monday.</p>
<pre tabindex="0"><code>$ TZ=UTC systemd-analyze calendar --iterations=2 &#39;Mon *-05~07/1&#39;
  Original form: Mon *-05~07/1
Normalized form: Mon *-05~07/1 00:00:00
    Next elapse: Mon 2027-05-31 00:00:00 UTC
       From now: 4 months 28 days left
   Iteration #2: Mon 2028-05-29 00:00:00 UTC
       From now: 1 year 4 months left
</code></pre><h3 id="weekday-ranges">Weekday ranges</h3>
<p>The week starts on Monday, and weekday ranges don’t wrap around its end. <code>Sat..Sun</code> works, but a long weekend from Friday to Monday has to be written as <code>Mon,Fri..Sun</code> (or a full list) instead of <code>Fri..Mon</code>.</p>
<pre tabindex="0"><code>$ TZ=UTC systemd-analyze calendar &#39;Sat..Sun&#39; &#39;Fri..Mon&#39;
  Original form: Sat..Sun
Normalized form: Sat,Sun *-*-* 00:00:00
    Next elapse: Sat 2027-01-02 00:00:00 UTC
       From now: 24h left

Failed to parse calendar specification &#39;Fri..Mon&#39;: Invalid argument
</code></pre><p><code>-</code> works as a range too, also for <a href="https://github.com/systemd/systemd/blob/v262/src/shared/calendarspec.c#L457">backwards compatibility</a>, and <code>Mon-Fri</code> turns into <code>Mon..Fri</code>. The man page only mentions <code>..</code>.</p>
<pre tabindex="0"><code>$ TZ=UTC systemd-analyze calendar Mon-Fri
  Original form: Mon-Fri
Normalized form: Mon..Fri *-*-* 00:00:00
    Next elapse: Mon 2027-01-04 00:00:00 UTC
       From now: 3 days left
</code></pre><h3 id="limits">Limits</h3>
<p>Years have to be between 1970 and 2199, and anything outside that range is rejected (<code>2200-01-01</code> is fine as a timestamp, as the hint points out). Inside it, an event can still be valid and never elapse, e.g., February 30 or a weekday that doesn’t match a fixed date. Only the weekday gets a warning. The upper limit also keeps the search for the next elapse from looping forever on impossible dates like February 30 (<a href="https://github.com/systemd/systemd/blob/v262/src/shared/calendarspec.c#L1187">source</a>).</p>
<pre tabindex="0"><code>$ TZ=UTC systemd-analyze calendar &#39;2199-12-31&#39; &#39;2200-01-01&#39; &#39;*-02-30&#39; &#39;Wed 2027-01-06&#39; &#39;Wed 2027-01-05&#39;
  Original form: 2199-12-31
Normalized form: 2199-12-31 00:00:00
    Next elapse: Tue 2199-12-31 00:00:00 UTC
       From now: 172 years 11 months left

Failed to parse calendar specification &#39;2200-01-01&#39;: Invalid argument
Hint: this expression is a valid timestamp. Use &#39;systemd-analyze timestamp &#34;2200-01-01&#34;&#39; instead?

  Original form: *-02-30
Normalized form: *-02-30 00:00:00
    Next elapse: never

  Original form: Wed 2027-01-06
Normalized form: Wed 2027-01-06 00:00:00
    Next elapse: Wed 2027-01-06 00:00:00 UTC
       From now: 5 days left

Weekday constraint does not match the fixed date 2027-01-05 (which is a Tue), so this timer will never elapse.
  Original form: Wed 2027-01-05
Normalized form: Wed 2027-01-05 00:00:00
    Next elapse: never
</code></pre><h3 id="daylight-saving-time">Daylight saving time</h3>
<p>The man page doesn’t mention daylight saving time at all. Calendar events use local time unless they have a timezone, so a skipped/repeated hour affects every event in it. In New York, clocks jump from 02:00 to 03:00 on 2027-03-14, so <code>02:30</code> doesn’t exist that day.</p>
<pre tabindex="0"><code>$ TZ=America/New_York systemd-analyze calendar --base-time=&#39;2027-03-13 12:00&#39; --iterations=2 &#39;02:30&#39;
  Original form: 02:30
Normalized form: *-*-* 02:30:00
    Next elapse: Mon 2027-03-15 02:30:00 EDT
       (in UTC): Mon 2027-03-15 06:30:00 UTC
       From now: 2 months 12 days left
   Iteration #2: Tue 2027-03-16 02:30:00 EDT
       (in UTC): Tue 2027-03-16 06:30:00 UTC
       From now: 2 months 13 days left
</code></pre><p>Instead of moving to 03:30, the event skips 2027-03-14 entirely. On 2027-11-07, clocks go back from 02:00 to 01:00, so the hour from 01:00 to 02:00 happens twice. <code>01:30</code> elapses in the first one (EDT), and the next elapse after that is a day later, not an hour.</p>
<pre tabindex="0"><code>$ TZ=America/New_York systemd-analyze calendar --base-time=&#39;2027-11-06 12:00&#39; --iterations=2 &#39;01:30&#39;
  Original form: 01:30
Normalized form: *-*-* 01:30:00
    Next elapse: Sun 2027-11-07 01:30:00 EDT
       (in UTC): Sun 2027-11-07 05:30:00 UTC
       From now: 10 months 5 days left
   Iteration #2: Mon 2027-11-08 01:30:00 EST
       (in UTC): Mon 2027-11-08 06:30:00 UTC
       From now: 10 months 6 days left
</code></pre><p><code>hourly</code> leaves out the repeated hour too, so after 01:00 EDT it elapses next at 02:00 EST, 2 hours later.</p>
<pre tabindex="0"><code>$ TZ=America/New_York systemd-analyze calendar --base-time=&#39;2027-11-07 00:00&#39; --iterations=3 hourly
  Original form: hourly
Normalized form: *-*-* *:00:00
    Next elapse: Sun 2027-11-07 01:00:00 EDT
       (in UTC): Sun 2027-11-07 05:00:00 UTC
       From now: 10 months 5 days left
   Iteration #2: Sun 2027-11-07 02:00:00 EST
       (in UTC): Sun 2027-11-07 07:00:00 UTC
       From now: 10 months 5 days left
   Iteration #3: Sun 2027-11-07 03:00:00 EST
       (in UTC): Sun 2027-11-07 08:00:00 UTC
       From now: 10 months 5 days left
</code></pre><p>Timestamps do the opposite in both cases. A time that doesn’t exist moves an hour forward instead of to the next day, and a repeated one means the second time (EST).</p>
<pre tabindex="0"><code>$ TZ=America/New_York systemd-analyze timestamp &#39;2027-03-14 02:30&#39; &#39;2027-11-07 01:30&#39;
  Original form: 2027-03-14 02:30
Normalized form: Sun 2027-03-14 03:30:00 EDT
       (in UTC): Sun 2027-03-14 07:30:00 UTC
   UNIX seconds: @1805009400
       From now: 2 months 11 days left

  Original form: 2027-11-07 01:30
Normalized form: Sun 2027-11-07 01:30:00 EST
       (in UTC): Sun 2027-11-07 06:30:00 UTC
   UNIX seconds: @1825569000
       From now: 10 months 5 days left
</code></pre><p>An event with <code>UTC</code> behind it (e.g., <code>*-*-* 01:30 UTC</code>) isn’t affected.</p>
<h3 id="timezones-in-events">Timezones in events</h3>
<p>Offsets and <code>Z</code> don’t work in calendar events, even though the man page says their timezones are similar to the ones in timestamps.</p>
<pre tabindex="0"><code>$ TZ=UTC systemd-analyze calendar &#39;12:00 +05:00&#39; &#39;12:00 Z&#39;
Failed to parse calendar specification &#39;12:00 +05:00&#39;: Invalid argument
Hint: this expression is a valid timestamp. Use &#39;systemd-analyze timestamp &#34;12:00 +05:00&#34;&#39; instead?

Failed to parse calendar specification &#39;12:00 Z&#39;: Invalid argument
Hint: this expression is a valid timestamp. Use &#39;systemd-analyze timestamp &#34;12:00 Z&#34;&#39; instead?
</code></pre><p>A local abbreviation <a href="https://github.com/systemd/systemd/blob/v262/src/shared/calendarspec.c#L922">sets daylight saving time</a> here too, but for every elapse. In New York, <code>12:00 EST</code> stops elapsing once summer time starts on 2027-03-14, so only 2 of 3 iterations show up.</p>
<pre tabindex="0"><code>$ TZ=America/New_York systemd-analyze calendar --base-time=&#39;2027-03-12 00:00&#39; --iterations=3 &#39;12:00 EST&#39;
  Original form: 12:00 EST
Normalized form: *-*-* 12:00:00 EST
    Next elapse: Fri 2027-03-12 12:00:00 EST
       (in UTC): Fri 2027-03-12 17:00:00 UTC
       From now: 2 months 9 days left
   Iteration #2: Sat 2027-03-13 12:00:00 EST
       (in UTC): Sat 2027-03-13 17:00:00 UTC
       From now: 2 months 10 days left
</code></pre>]]></content:encoded></item></channel></rss>