Tony G. writes: > They are supposed to have GMT: In these modern times UTC is generally a better universal standard than GMT.
> But the timezone file in */etc/localtime* is the same on them: > md5sum /usr/share/zoneinfo/* 2>/dev/null|grep $(md5sum /etc/localtime|cut > -d" " -f1) > fcccbcf95c718cf2fdee557763e460be /usr/share/zoneinfo/GMT > fcccbcf95c718cf2fdee557763e460be /usr/share/zoneinfo/GMT0 > fcccbcf95c718cf2fdee557763e460be /usr/share/zoneinfo/GMT-0 > fcccbcf95c718cf2fdee557763e460be /usr/share/zoneinfo/GMT+0 > fcccbcf95c718cf2fdee557763e460be /usr/share/zoneinfo/Greenwich > > Could the /etc/sysconfig/clock file cause this? UNIX time is based on the number of seconds since January 1, 1970 00:00 UTC. This is converted to local time for display based on the TZ environment variable, with /etc/localtime specifying the default local time conversions rule (and usually a copy or link to a corresponding rule file in /usr/share/zoneinfo). /etc/sysconfig/clock has only to do with management of the hardware clock. The ZONE setting in combination with the UTC boolean determine whether the hardware clock is treated as local time or UTC when the hardware clock is set from the UNIX clock during shutdown. For most server configurations it is advisable to manage the hardware clock in UTC (UTC=true). In particular this can avoid some problems with reboots around daylight savings time changes introducing 1 hour offsets. -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-us...@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
