cron is not timezone aware on per line base

Bug #858583 reported by ABorland
14
This bug affects 3 people
Affects Status Importance Assigned to Milestone
cron (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

We need to specify many different cronjobs in many different timezones

http://blogs.oracle.com/chrisg/entry/timezone_aware_cron_finally_pushed
OpenSolaris finally contains a version of cron that understands and correctly handles having different timezones. You can also specify a different home directory (useful when you don't want NFS to get involved in your cron job for any reason) and shell to run jobs in. It should be in build 106 of OpenSolaris & Nevada.
This brings you crontab in line with at(1) which has been timezone aware for some time.
To use simply set the variables HOME, TZ and SHELL in your crontab file and all subsequent lines will use those values until the next HOME, TZ and SHELL lines are found:

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in cron (Ubuntu):
status: New → Confirmed
Revision history for this message
Matt Panaro (matt-extensicom) wrote :

redhat/fedora supports CRON_TZ now as well

Revision history for this message
Rostislav (rostislav-kouznetsov) wrote :

The issue is still there in 20.04: cron ignores CRON_TZ in crontab.
Suse cron respects CRON_TZ variable.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.