You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I just got an issue for raspiBackup and finally it turned out the root cause for the issue is located in raspi-config. The user used raspi-config to change the timezone and detected cron starts tasks at an incorrect time. According this page a restart of cron has to be done whenever the timezone was changed.
It's not a serious issue because sooner or later the Raspberry will be restarted but it's a nasty issue in particular for beginners. I suggest to restart cron when the timezone is changed in raspi-config.
The text was updated successfully, but these errors were encountered:
Right, but what makes cron special to any other software that may not cope with a timezone change?
Since we don't know what other software may be affected, it seems like a restart is the right solution, as suggested on the page you linked. Otherwise we'd be playing whackamole with all the special cases that may need to be handled.
On the other hand, I don't have a strong preference either. Given that this is the first time anybody has noticed this, it's unlikely to come up again with other software, so just handling cron makes sense as well.
So maybe we should restart cron and then if the problem is reported again with other software, we can prompt for a reboot rather than adding special cases.
I just got an issue for raspiBackup and finally it turned out the root cause for the issue is located in raspi-config. The user used raspi-config to change the timezone and detected cron starts tasks at an incorrect time. According this page a restart of cron has to be done whenever the timezone was changed.
It's not a serious issue because sooner or later the Raspberry will be restarted but it's a nasty issue in particular for beginners. I suggest to restart cron when the timezone is changed in raspi-config.
The text was updated successfully, but these errors were encountered: