Bug 439720 - tzdata upgrade should restart crond and atd
Summary: tzdata upgrade should restart crond and atd
Alias: None
Product: Fedora
Classification: Fedora
Component: cronie
Version: 8
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Marcela Mašláňová
QA Contact: Fedora Extras Quality Assurance
: 439719 (view as bug list)
Depends On:
TreeView+ depends on / blocked
Reported: 2008-03-30 22:47 UTC by JW
Modified: 2008-06-26 06:33 UTC (History)
0 users

Clone Of:
Last Closed: 2008-03-31 15:18:57 UTC

Attachments (Terms of Use)

Description JW 2008-03-30 22:47:16 UTC
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):

How reproducible:

Steps to Reproduce:
1. upgrade tzdata rpm
Actual results:
crond not restarted
atd not restarted

Expected results:
crond needs to be restarted to pick up the changes
atd probably needs to be restarted also

Additional info:

Comment 1 Petr Machata 2008-03-31 11:00:28 UTC
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!

Comment 2 Marcela Mašláňová 2008-03-31 14:50:22 UTC
*** Bug 439719 has been marked as a duplicate of this bug. ***

Comment 3 Marcela Mašláňová 2008-03-31 15:18:57 UTC
I'll add trigger into cronie.

Comment 4 Subhendu Ghosh 2008-06-26 06:33:30 UTC
any update on the trigger?

Note You need to log in before you can comment on or make changes to this bug.