[BUGS] Don't get caught this sunday with no DST changes

[jonathan michaels]

On Thu, Mar 27, 2008 at 08:16:54PM +1100, Edwin Groothuis wrote:
> On Thu, Mar 27, 2008 at 08:09:13PM +1100, jonathan michaels wrote:
> > > At http://www.mavetju.org/weblog/html/00223.html I have a write up
> > > on how to see if your systems need updating for coming Sundays
> > > absence of DST changes.
> > 
> > i noticed some odd things in teh 00223.html page
> > 
> > $ wget ftp://ftp://elsie.nci.nih.gov/pub/tzdata2008X.tar.gz
> 
> That double ftp:// happens if you blindly copy and paste :-)

sooy this is teh second time my poor cooms skills caugth me
today, what i meant to say is that it was like that in teh
original and i copied it as was in teh posted page then made
teh changes and got teh file after i had a look and worked out
its correct name .. i was trying to tell teh rest of teh people
that might use this to not blinldy cut/paste .. one day i'll
get this right ??
 
> > the front bit seems to be a typo, yes ?? and teh actual name of
> > teh relevent file is tzdata2008b.tar.gz
> 
> I didn't use the "b" because it changes so often and it will thus
> be obsolete in three weeks anyway.
> 
> > then i did teh usual zic and copied files and when i tried to
> > check teh date/time going forward i discovered something odd
> > for example,
> 
> You did check if the time *before* was incorrect, didn't you?

yes, i did do that and it came in as on teh posted page

 
> > 
> > $ perl -e 'use POSIX;print "Date = ", POSIX::ctime(1206529200 + 86400 * 0);'
> > Date = Wed Mar 26 22:00:00 2008
> > 
> > $ perl -e 'use POSIX;print "Date = ", POSIX::ctime(1206529200 + 86400 * 7);'
> > Date = Wed Apr  2 22:00:00 2008
> > 
> > $ perl -e 'use POSIX;print "Date = ", POSIX::ctime(1206529200 + 86400 * 14);'
> > Date = Wed Apr  9 21:00:00 2008
> > 
> > i thought i'd gotten it nailed but then i tried the last one
> > and saw the 21:00:00, again.  just to check if it is not an
> > anomily i also tried one at 28 days, as well as using the shell
> > scripts one liners as per provided examples.
> 
> That's the expected result: It should be 22:00 on the second wednesday
> and 21:00 in the third wednesday.

sorry edwing it seems to me that i have missed something here
but i don't seem to be able to work out what it is that i have
missed, my brain is telling me that i am supposed to be seeing
teh 22:00:00 going forward .. i am stuck in a closed loop that
i cannot break out off, i would appreciate some help please.

much kind regards and sppreciations

jonathan

stuck behind a locked door, the keys are on teh other side. 

-- 
================================================================
powered by ..
QNX, OS9 and freeBSD  --  http://caamora com au/operating system
==== === appropriate solution in an inappropriate world === ====