It just makes the design more complex (there’s at least one extra nasty corner case I can think of) and generally doesn’t add that much a performance improvement vs “run every 30 minutes”, to be worth it, IMHO.
Eh, if the script always just calculates the sunrise time for the next day and overwrites the cron job, then its runtime shouldn’t matter — unless it gets stuck for 24 hours.
Couldn’t you make whatever script your cron job runs also adjust the timing of the cron job to move with the sunrise / sunset?
You could.
It just makes the design more complex (there’s at least one extra nasty corner case I can think of) and generally doesn’t add that much a performance improvement vs “run every 30 minutes”, to be worth it, IMHO.
Well, now I’m curious about what that corner case is.
The script can be triggered just before and run during the time that’s calculated as the transition from nighttime to daytime.
If that possibility is not taken in account in the implementation there’s a risk that the cron job is scheduled for a bit under 24h later.
It’s basically a critical race condition.
Eh, if the script always just calculates the sunrise time for the next day and overwrites the cron job, then its runtime shouldn’t matter — unless it gets stuck for 24 hours.
Yeah, if the script only ever schedules the next day’s run, that would work fine.