Work at SourceForge, help us to make it a better place! We have an immediate need for a Support Technician in our San Francisco or Denver office.

Close

#1620 clock scan - aberant behaviour

obsolete: 8.3
closed-works-for-me
Kevin B KENNY
5
2003-02-16
2001-09-07
Anonymous
No

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

Discussion

    • labels: 105657 --> 06. Time Measurement
    • assigned_to: dkf --> kennykb
     
  • Kevin B KENNY
    Kevin B KENNY
    2003-02-16

    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.

     
  • Kevin B KENNY
    Kevin B KENNY
    2003-02-16

    • status: open --> closed-works-for-me