Bug 439719

Summary: crond does not detect changes to /etc/localtime
Product: [Fedora] Fedora Reporter: JW <ohtmvyyn>
Component: vixie-cronAssignee: Marcela Mašláňová <mmaslano>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: low    
Version: 8   
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2008-03-31 14:50:21 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description JW 2008-03-30 22:44:16 UTC 
Description of problem:
crond does not detect changes to /etc/localtime.  That is, should one's timezone
dst change and require upgrade of tzdata, crond continues on as if nothing has
changes.  crond needs to be restarted.

Version-Release number of selected component (if applicable):
vixie-cron-4.2-3.fc8

How reproducible:
Always

Steps to Reproduce:
1. change local timezone rules for daylight-saving-time eg by upgrading tzdata rpm
  
Actual results:
crond continues as though nothing has changed

Expected results:
crond should check whether /etc/localtime timestamp has changed


Additional info:
Comment 1 Marcela Mašláňová 2008-03-31 14:50:21 UTC 

*** This bug has been marked as a duplicate of 439720 ***