| 1 |
On Sun, Mar 29, 2015 at 4:32 PM, Marc Joliet <marcec@×××.de> wrote: |
| 2 |
> |
| 3 |
> Am Sun, 29 Mar 2015 12:48:18 -0600 |
| 4 |
> schrieb Canek Peláez Valdés <caneko@×××××.com>: |
| 5 |
> |
| 6 |
> [...] |
| 7 |
> > Are you really sure "0/2:00" means "every 2 hours"? I don't see an |
| 8 |
explicit |
| 9 |
> > mention in man 7 systemd.time that 0 means "*-*-* 00:00:00". It really |
| 10 |
> > worked bi-hourly before? |
| 11 |
> |
| 12 |
> Yes, it definitely worked before (I've been running this and other timers |
| 13 |
for |
| 14 |
> about a month). I don't remember how I inferred that rule, but I think it |
| 15 |
was |
| 16 |
> this bit from systemd.time(7): |
| 17 |
> |
| 18 |
> "Either time or date specification may be omitted, in which case the |
| 19 |
> current day and 00:00:00 is implied, respectively. If the second |
| 20 |
component |
| 21 |
> is not specified, ":00" is assumed." |
| 22 |
> |
| 23 |
> But I don't see any definition for these components, so maybe I'm wrong |
| 24 |
and my |
| 25 |
> timer only works by accident. |
| 26 |
> |
| 27 |
> > Either way, it cretainly could be a bug. |
| 28 |
> |
| 29 |
> Perhaps, since it's back to the way it was before: |
| 30 |
> |
| 31 |
> # systemctl list-timers |
| 32 |
> NEXT LEFT LAST |
| 33 |
PASSED UNIT ACTIVATES |
| 34 |
> Mo 2015-03-30 02:00:00 CEST 1h 44min left Mo 2015-03-30 00:00:00 |
| 35 |
CEST 15min ago backup-hourly.timer |
| 36 |
backup@××××××.service |
| 37 |
> [...] |
| 38 |
|
| 39 |
Perhaps the bug is only in how systemctl presents the information. |
| 40 |
|
| 41 |
Regards. |
| 42 |
-- |
| 43 |
Canek Peláez Valdés |
| 44 |
Profesor de asignatura, Facultad de Ciencias |
| 45 |
Universidad Nacional Autónoma de México |
Archives