Florin Andrei wrote:
Stephen Harris wrote:
Any process started before you update /etc/localtime (and ensure that
got updated correctly; it may not have been) may need to be restarted
if it uses zoneinfo information. Two obvious ones are syslog and cron.
The safest solution is to reboot.
OK. So let me see if I get this right:
# ls -l /etc/localtime
-rw-r--r-- 1 root root 1017 May 5 2006 /etc/localtime
# rpm -qf /etc/localtime
glibc-2.3.4-2.19
I've found the rpm updates for tzdata don't always update localtime.
safest is to
cp /usr/zoneinfo/YOURTIMEZONE /etc/localtime
then reboot
The system also has tzdata-2007c
So /etc/localtime hasn't been touched in a long time, but tzdata has
been updated recently. That means, all daemons that haven't been
restarted since /etc/localtime has been updated, need a restart. Right?
By the way, the system passes the empirical US DST '07 test (there's a
1 hour difference between the two outputs - if they were identical
that would be a problem):
# date --date="Mar 25 15:00:00 UTC 2006"
Sat Mar 25 07:00:00 PST 2006
# date --date="Mar 25 15:00:00 UTC 2007"
Sun Mar 25 08:00:00 PDT 2007
the US timezone changes triggered by the Energy Plunder Act of 2005 have
been in every tzdata since 2006a (and maybe earlier)
_______________________________________________
CentOS mailing list
CentOS@xxxxxxxxxx
http://lists.centos.org/mailman/listinfo/centos
