Chris Down
a8c3ac6672
When parsing an absolute time specification like `hh:mm` for the `shutdown` command, the code interprets a time in the past as "tomorrow at this time". It currently implements this by adding a fixed 24-hour duration (`USEC_PER_DAY`) to the timestamp. This assumption breaks across DST transitions, as the day might not be 24 hours long. This can cause the shutdown to be scheduled at the wrong time (typically off by one hour in either direction). Change the logic to perform calendar arithmetic instead of timestamp arithmetic. If the calculated time is in the past, we increment `tm.tm_mday` and call `mktime_or_timegm_usec()` a second time. This delegates all date normalization logic to `mktime()`, which correctly handles all edge cases, including DST transitions, month-end rollovers, and leap years. Fixes: https://github.com/systemd/systemd/issues/39232
System and Service Manager
Details
Most documentation is available on systemd's web site.
Assorted, older, general information about systemd can be found in the systemd Wiki.
Information about build requirements is provided in the README file.
Consult our NEWS file for information about what's new in the most recent systemd versions.
Please see the Code Map for information about this repository's layout and content.
Please see the Hacking guide for information on how to hack on systemd and test your modifications.
Please see our Contribution Guidelines for more information about filing GitHub Issues and posting GitHub Pull Requests.
When preparing patches for systemd, please follow our Coding Style Guidelines.
If you are looking for support, please contact our mailing list, join our IRC channel #systemd on libera.chat or Matrix channel
Stable branches with backported patches are available in the stable repo.
We have a security bug bounty program sponsored by the Sovereign Tech Fund hosted on YesWeHack
Repositories with distribution packages built from git main are available on OBS