[Tcl-bugs] [ tcl-Bugs-459508 ] clock scan - aberant behaviour

[SourceForge.net <no...@so...>]

Bugs item #459508, was opened at 2001-09-07 08:38
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=110894&aid=459508&group_id=10894

Category: 06. Time Measurement
Group: = 8.3
>Status: Closed
>Resolution: Works For Me
Priority: 5
Submitted By: Nobody/Anonymous (nobody)
Assigned to: Kevin B KENNY (kennykb)
Summary: clock scan - aberant behaviour

Initial Comment:
On Solaris 2.8 (SPARC U10) the following command:
"clock scan "19700101T00:00:00" issued twice returns
diferent
outputs.
My ltimezone is EET.

Ex:

bash-2.03$ tclsh
%  clock scan "19700104T00:00:00"
252000
%  clock scan "19700104T00:00:00"
248400



----------------------------------------------------------------------

>Comment By: Kevin B KENNY (kennykb)
Date: 2003-02-16 14:41

Message:
Logged In: YES 
user_id=99768

I just tried this a number of ways on Solaris 2.8, and consistently
got the (correct) value of 248400.

I'm at a loss to explain the one-hour difference that the original
submitter reports. Had it been three or four hours, I'd speculate
that there was another thread manipulating $env(TZ) at the time,
in order to execute [clock format ... -gmt true].  If that were the
case, though, then recent changes to tclClock.c have fixed the
problem anyway.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=110894&aid=459508&group_id=10894