Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Restart of cron missing when timezone is updated #111

Open
framps opened this issue Apr 13, 2020 · 3 comments
Open

Restart of cron missing when timezone is updated #111

framps opened this issue Apr 13, 2020 · 3 comments

Comments

@framps
Copy link

framps commented Apr 13, 2020

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.

@XECDesign
Copy link
Member

It seems like this wouldn't be a problem unique to cron and raspi-config should prompt the user to restart the system instead.

@framps
Copy link
Author

framps commented Apr 14, 2020

I don't think a user of raspi-config should be prompted for a restart all the time. systemctl restart cron will restart cron very quickly.

@XECDesign
Copy link
Member

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants