On Sun, Mar 29, 2015 at 5:27 AM, Marc Joliet <mar...@gmx.de> wrote: > > Hi list > > I've got a weird problem: after booting my computer (which was off during the > DST change last night) my bi-hourly backup timer didn't run as it would > normally do. Looking at the list of timers, it is next scheduled to run at > midnight tonight: > > # systemctl list-timers > NEXT LEFT LAST PASSED UNIT ACTIVATES > [...] > Mo 2015-03-30 00:00:00 CEST 10h left So 2015-03-29 00:00:01 CET 12h ago backup-hourly.timer backup@hourly.service > [...] > > The timer is defined thusly: > > # cat /etc/systemd/system/backup-hourly.timer > [Unit] > Description=Run hourly backups (timer) > > [Timer] > OnCalendar=0/2:00 > Persistent=True > Unit=backup@hourly.service > > [Install] > WantedBy=timers.target > > Has anybody else seen anything similar today? I've never seen anything like > this happen before, so I wouldn't be surprised if it's related to the DST > change. Also, in the event that it matters: I use chrony instead of timesyncd.
Are you really sure "0/2:00" means "every 2 hours"? I don't see an explicit mention in man 7 systemd.time that 0 means "*-*-* 00:00:00". It really worked bi-hourly before? Either way, it cretainly could be a bug. Regards. -- Canek Peláez Valdés Profesor de asignatura, Facultad de Ciencias Universidad Nacional Autónoma de México
