That is why you run your jobs on GMT/UTC and not display time.

I guess that is what I'm trying to show in the above example. You could technically shift your UTC jobs by running your own NTP server and desyncing it from UTC by the offset you want. It would work, but it would be nightmare fuel. And possibly this is an even better example of what DST is doing.

▲

kuboble a day ago | parent | prev | next [-]

Well, it's not that obvious.

Some jobs should run every day at 8 am (e.g. torn on the temporary speed limit on front of the school), vs tasks that should actually run every 24h (e.g. feed the bacteria in exact time intervals)

▲

edoceo a day ago | parent | prev [-]

The jobs need to run at midnight, local time. Which shifts from UTC. How to handle?

▲

defrost a day ago | parent | next [-]

Why does it need to run at that time?

* If it's being run to scrap data from a source that's available at some time, adjust the job if the source changes its time.

* If it's being run "when its dark and no one is around" then it'll run at some part of the dark bit regardless of DST changes.

	▲	Retric a day ago \| parent [-]
		Sometimes you minimize downtime by running something while some other system you don’t control is down.

▲

ssl-3 a day ago | parent | prev [-]

Use UTC, and stop faffing about with changing localtime twice every year so the offset is a constant?