I've been using this command to check:

zdump -v Canada/Eastern |grep 2007

which returns the correct DST settings on my CAM and CAS. Your command 
returns the correct settings on my CAM, but the old DST settings on my 
CAS. Which is right?

-Mike


On Tue, 6 Feb 2007, Bruce A. Locke wrote:

> I was poking around our CCA Manager server to see if the version of
> Fedora Linux that it uses was updated for the upcoming changes to
> Daylight Savings Time in the US.
>
> The output of "zdump -v /etc/localtime | grep 2007" on our system shows:
>
> /etc/localtime  Sun Apr  1 06:59:59 2007 UTC = Sun Apr  1 01:59:59 2007
> EST isdst=0 gmtoff=-18000
> /etc/localtime  Sun Apr  1 07:00:00 2007 UTC = Sun Apr  1 03:00:00 2007
> EDT isdst=1 gmtoff=-14400
> /etc/localtime  Sun Oct 28 05:59:59 2007 UTC = Sun Oct 28 01:59:59 2007
> EDT isdst=1 gmtoff=-14400
> /etc/localtime  Sun Oct 28 06:00:00 2007 UTC = Sun Oct 28 01:00:00 2007
> EST isdst=0 gmtoff=-18000
>
> The file does not contain the DST update.  But the copy of the New_York
> timezone file in /usr/share/zoneinfo/America/New_York does:
>
> /usr/share/zoneinfo/America/New_York  Sun Mar 11 06:59:59 2007 UTC = Sun
> Mar 11 01:59:59 2007 EST isdst=0 gmtoff=-18000
> /usr/share/zoneinfo/America/New_York  Sun Mar 11 07:00:00 2007 UTC = Sun
> Mar 11 03:00:00 2007 EDT isdst=1 gmtoff=-14400
> /usr/share/zoneinfo/America/New_York  Sun Nov  4 05:59:59 2007 UTC = Sun
> Nov  4 01:59:59 2007 EDT isdst=1 gmtoff=-14400
> /usr/share/zoneinfo/America/New_York  Sun Nov  4 06:00:00 2007 UTC = Sun
> Nov  4 01:00:00 2007 EST isdst=0 gmtoff=-18000
>
> The timestamp on /etc/localtime matches the day we did the destructive
> reinstall up to 3.6.0(?) which was on December 29, 2005.  The timestamp
> for /usr/share/zoneinfo/America/New_York was on May 11, 2006.
>
> It looks like the tzdata package was updated somewhere around CCA 4.0.4
> and the update did not contain the corresponding glibc-common upgrade
> from Fedora.  The glibc-common package usually has a trigger that
> updates /etc/localtime if tzdata is also updated.  So unless such a
> trigger was added to tzdata in Cisco's forked version or put in the
> update script for CCA then /etc/localtime will never be updated.  I
> don't see such an update in their script but I could have very well
> missed it.
>
> Is this a known issue?  The resolved caveats list for 4.0.3.3 shows
> CSCsg44268 but shouldn't /etc/localtime be updated for that?  Has anyone
> else seen this on their systems?  It may very well be a fluke with our
> local environment but I just want to be sure.
>
> Thanks.
>
> -- 
> Bruce A. Locke
> [log in to unmask]
> HAB 50 - (845) 257-3809
>
> Network Administrator
> Computer Services
> State University of New York at New Paltz
>


             _________________________________________

Mike Diggins       			Voice:  905.525.9140 Ext. 27471
Network Analyst, Enterprise Networks    FAX:    905.528.3773
University Technology Services 		E-Mail: [log in to unmask]
McMaster University, Hamilton, Ontario