FS#48281 - [systemd] timer unit OnCalendar calculates wrong execution date
Attached to Project:
Arch Linux
Opened by Manfred Miederer (LessWire) - Sunday, 21 February 2016, 02:19 GMT
Last edited by Dave Reisner (falconindy) - Monday, 22 February 2016, 12:36 GMT
Opened by Manfred Miederer (LessWire) - Sunday, 21 February 2016, 02:19 GMT
Last edited by Dave Reisner (falconindy) - Monday, 22 February 2016, 12:36 GMT
|
Details
Description:
This happens at least using CET time (24 hours) and a timer controlled service which uses 'OnCalendar=' Example: Let's say current date and time is: Sunday, 9:00 CET Unit file 'test.timer' contains: [code] [Unit] ... [Timer] OnCalendar=Sun 16:00:00 [Install] WantedBy=multi-user.target [/code] The corresponding 'test.service' should be executed 7 hours later but it don't! 'systemctl list-timers' shows next execution for a week later (Sunday next week and not for today). This happens with systemd 229-2, downgrading to 228-4 helps and it works fine. |
This task depends upon
Closed by Dave Reisner (falconindy)
Monday, 22 February 2016, 12:36 GMT
Reason for closing: Upstream
Additional comments about closing: https://github.com/systemd/systemd/issue s/2682
Monday, 22 February 2016, 12:36 GMT
Reason for closing: Upstream
Additional comments about closing: https://github.com/systemd/systemd/issue s/2682
Comment by
Dave Reisner (falconindy) - Sunday,
21 February 2016, 14:55 GMT
Comment by
Manfred Miederer (LessWire) -
Sunday, 21 February 2016, 16:42 GMT
Comment by
Dave Reisner (falconindy) - Sunday,
21 February 2016, 18:20 GMT
Comment by
Manfred Miederer (LessWire) -
Sunday, 21 February 2016, 18:27 GMT
Please report this upstream.
Ok, i did.
And the link you were supposed to include with that seems like it
might be this one:
https://github.com/systemd/systemd/issues/2682
That's right, thanks.