All Topics
All Topics
Technology
Technology
Design
Design
Programming
Programming
Science
Science
News
News
Gaming
Gaming
Entertainment
Entertainment
Business
Business
Finance
Finance
Sports
Sports
Health
Health
Food
Food
Travel
Travel
Art
Art
Music
Music
Books
Books
Education
Education
Politics
Politics
Personal
Personal
No algorithm. No AI slop. No ads. Just RSS. Pro-human. Indie writers. Real journalism. Open web. Chronological. Hand toasted.

Avoid Scheduling Cron Jobs at 2-3 AM Due to Daylight Saving Time Issues

By

pera

7mo ago· 2 min readen

Summary

The article warns against scheduling cron jobs (automated tasks) for 2:00 am or 3:00 am on Sunday mornings due to daylight saving time transitions. It explains that while such jobs usually run fine, twice per year when daylight saving time begins or ends, these jobs can experience strange behavior, potentially running multiple times per second or not at all. The advice extends to avoiding these times on other days as well, since cron job schedules might be changed later.

Key quotes

· 3 pulled
A word to the wise: Do not set any cron jobs for 2:00 am or 3:00 am on Sunday morning!
Most of the time such cron jobs will run fine, but if they run every Sunday morning, then twice per year they will run at the exact time daylight savings time (aka summer time) kicks in or ends, sometimes with very strange results.
Or to be safe, on other mornings besides Sunday as well, since jobs originally set to run on some particular day may eventually be changed to run on another day, or every day.
Snippet from the RSS feed
A word to the wise: Do not set any cron jobs for 2:00 am or 3:00 am on Sunday morning! Or to be safe, on other mornings besides Sunday as well, since jobs originally set to run on some particular day may eventually be changed to run on another day, or eve

You might also wanna read