Odd thing I noticed this morning, my ZFS scrub didn't happen over the weekend as it usually does.
So I started to investigate. #nixos
This didn't end up where I expected.
Odd thing I noticed this morning, my ZFS scrub didn't happen over the weekend as it usually does.
So I started to investigate. #nixos
This didn't end up where I expected.
So I looked at the timer itself.
The definition is:
```
[Timer]
OnCalendar=Sun, 02:00
Persistent=yes
```
Right, now it's obvious, 02:00 didn't happen this last Sunday. 01:59:59 -> 03:00:00.
So... yeah, I don't know what I expected but I didn't really expect it to skip it. This isn't a complaint or a bug. It's just another realization of why #DST is terrible.
So to investigate this, I started by checking the status on the service. Last run was the weekend two weeks ago and hadn't been triggered since.
So I did a `systemctl list-timers`, last scheduled run was two weeks ago, next is this Sunday.
So why did it skip this Sunday?
@sa0bse I’ve seen similar stuff happening. The price of DST is not zero.
Out of sheer curiosity, the computer in question whas not configured to run on UTC then?
@giffengrabber Not on UTC no. I should probably change that.
@uint8_t Yes, I've also realized that everything 02:00:00 -> 02:59:59 would run twice within an hour once a year.
@sa0bse if I were me, I would never schedule tasks to run between [02:00:00, 03:00:00]
@sa0bse or another argument for using UTC on servers...
GNU social JP is a social network, courtesy of GNU social JP管理人. It runs on GNU social, version 2.0.2-dev, available under the GNU Affero General Public License.
All GNU social JP content and data are available under the Creative Commons Attribution 3.0 license.