What happens to at jobs across the DST switch?

[Bo Berglund]

On Sat, 27 Mar 2021 09:21:27 +1100, Karl Auer <kauer at biplane.com.au> wrote:

>It may be a display issue. Try it. Set up a task for X time UTC and see
>when it actually runs. If it runs at X time UTC, problem solved. If it
>runs at X time local, then you do actually have a problem. You still
>have a few hours to experiment with :-)

Set to run with: at 23:28 UTC
Should run at 00:28 CET
But runs at 23:28 CET

Seems like at does not error out on the UTC string in the argument but also does
not do anything with it...

Now I need to edit my script for Sunday such that it "understands" that when the
time should get to 2:00 it actually jumps to 3:00 instead.

I really wonder how this will work in the fall when time goes backwards so
instead of becoming 2:00 it gets back to 1:00.
So for example 1:58 will happen twice that night...

The transfer this weekend is easier since there is no duplicated time period in
the night just one lost hour...


-- 
Bo Berglund
Developer in Sweden