Bug report
Posted: Mon Apr 09, 2012 7:20 am
It appears to be a bug in WinBox [not sure if it occurs via other methods, but I know it occurs in Winbox.]
If you go into System | Scheduler and add a new scheduled item, it appears to add the next run time based on GMT, and not on the localized time-zone as set in the TZ.
[It's easy enough to modify, but one expects it default to the current local time, not GMT time.
This will cause jobs NOT to run as one might expect. [Not for hours yet, or even nearly a day from now, depending on your offset to GMT.]
It should calculate the current local time as set in the TZ and arrange for the job to run at the current local time, rather than at GMT without the local TZ offset..
Details:
v5.12 on RB450G
If you go into System | Scheduler and add a new scheduled item, it appears to add the next run time based on GMT, and not on the localized time-zone as set in the TZ.
[It's easy enough to modify, but one expects it default to the current local time, not GMT time.
This will cause jobs NOT to run as one might expect. [Not for hours yet, or even nearly a day from now, depending on your offset to GMT.]
It should calculate the current local time as set in the TZ and arrange for the job to run at the current local time, rather than at GMT without the local TZ offset..
Details:
v5.12 on RB450G