| 1 |
On Sun, Mar 29, 2015 at 5:27 AM, Marc Joliet <marcec@×××.de> wrote: |
| 2 |
> |
| 3 |
> Hi list |
| 4 |
> |
| 5 |
> I've got a weird problem: after booting my computer (which was off during |
| 6 |
the |
| 7 |
> DST change last night) my bi-hourly backup timer didn't run as it would |
| 8 |
> normally do. Looking at the list of timers, it is next scheduled to run |
| 9 |
at |
| 10 |
> midnight tonight: |
| 11 |
> |
| 12 |
> # systemctl list-timers |
| 13 |
> NEXT LEFT LAST |
| 14 |
PASSED UNIT ACTIVATES |
| 15 |
> [...] |
| 16 |
> Mo 2015-03-30 00:00:00 CEST 10h left So 2015-03-29 00:00:01 CET |
| 17 |
12h ago backup-hourly.timer backup@××××××.service |
| 18 |
> [...] |
| 19 |
> |
| 20 |
> The timer is defined thusly: |
| 21 |
> |
| 22 |
> # cat /etc/systemd/system/backup-hourly.timer |
| 23 |
> [Unit] |
| 24 |
> Description=Run hourly backups (timer) |
| 25 |
> |
| 26 |
> [Timer] |
| 27 |
> OnCalendar=0/2:00 |
| 28 |
> Persistent=True |
| 29 |
> Unit=backup@××××××.service |
| 30 |
> |
| 31 |
> [Install] |
| 32 |
> WantedBy=timers.target |
| 33 |
> |
| 34 |
> Has anybody else seen anything similar today? I've never seen anything |
| 35 |
like |
| 36 |
> this happen before, so I wouldn't be surprised if it's related to the DST |
| 37 |
> change. Also, in the event that it matters: I use chrony instead of |
| 38 |
timesyncd. |
| 39 |
|
| 40 |
Are you really sure "0/2:00" means "every 2 hours"? I don't see an explicit |
| 41 |
mention in man 7 systemd.time that 0 means "*-*-* 00:00:00". It really |
| 42 |
worked bi-hourly before? |
| 43 |
|
| 44 |
Either way, it cretainly could be a bug. |
| 45 |
|
| 46 |
Regards. |
| 47 |
-- |
| 48 |
Canek Peláez Valdés |
| 49 |
Profesor de asignatura, Facultad de Ciencias |
| 50 |
Universidad Nacional Autónoma de México |
Archives