Description of problem:
tzdata rpm should restart crond when upgraded otherwise crond will continue as
though nothing has changed
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. upgrade tzdata rpm
crond not restarted
atd not restarted
crond needs to be restarted to pick up the changes
atd probably needs to be restarted also
If cron wishes to be restarted after the tzdata update, is should do so itself,
via an rpm trigger. This is not going to happen in tzdata, the package is too
low-level for that.
Moreover I think restart of the service is too coarse tool, and might be very
disrupting when run in server environment. But if the cron daemon recognized
some re-schedule signal (or if it does), the trigger could just send that signal
to the daemon, that would be just as good.
Anyway, reassigning to cronie, our NG vixie-cron replacement!
*** Bug 439719 has been marked as a duplicate of this bug. ***
I'll add trigger into cronie.
any update on the trigger?