Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#12166 - rc scripts are affected by local TZ variable
Attached to Project:
Arch Linux
Opened by Daniel Quinn (searchingfortao) - Tuesday, 18 November 2008, 00:23 GMT
Last edited by Hugo Doria (hdoria) - Saturday, 21 March 2009, 23:01 GMT
Opened by Daniel Quinn (searchingfortao) - Tuesday, 18 November 2008, 00:23 GMT
Last edited by Hugo Doria (hdoria) - Saturday, 21 March 2009, 23:01 GMT
|
DetailsDescription:
Start up scripts appear to be affected by a locally set TZ variable. In other words, if root has her environment TZ set to "Canada/Pacific" and runs /etc/rc.d/http restart and then PHP scripts running out of Apache report the time in Pacific time, despite the fact that /etc/localtime is set to UTC. Steps to reproduce: # export TZ="Canada/Pacific" # /etc/rc.d/http restart (test the time on a PHP script) # unset TZ # /etc/rc.d/http restart (test the time on a PHP script) A sample PHP script to use: <? print date('Y-m-d H:i:s'); ?> Expected Behaviour: Server daemons should always start in the system time. Suggested fix: The TIMEZONE variable in rc.conf could be renamed to TZ or some rc-script magic could go into setting TZ based on TIMZONE. |
This task depends upon
As for renaming TIMEZONE to TZ... Thomas, what do you think?
export TZ=$TIMEZONE ?
http://projects.archlinux.org/?p=initscripts.git;a=commitdiff;h=af3ac0dc954d96855555aa8cb12633494d465a77