Simple timestamp

--
 &nbsp;   ; &nbsp; Andreas Kupries <andreaskActiveState.com>
&nbsp;   ; &nbsp;  Developer http://www.ActiveState.com
&nbsp; &nbsp; &nbsp; &nbsp; Tel: +1 778-786-1122
 

-----Original Message-----
From: Bartis, Robert M (Bob) [mailto:activetcl-bounceslistserv.ActiveState.com]On Behalf Of Bartis, Robert M (Bob)
Sent: Wednesday, August 15, 2007 6:01 PM
To: activetcllistserv.ActiveState.com; RoTcl@yahoogroups.com; tcltk@yahoogroups.com
Subject: Simple timestamp

All

 

I have loaded the most current Tcl distribution from the ActiveState site down to a local UNIX server. The application includes a basic logging function which prefixes all messages sent to be logged with a timestamp.

 

e.g

proc log {

set ts [clock format [clock seconds]]

puts "$ts - $msg"

}

The problem I am having is the value returned from [clock format [clock seconds]] jumps all over the place. Both the time, day, month and year come back with inaccurate values (e.g. Thu Apr 04 14:24:38 CDT 1912).&nbsp; All value are valid, just do not reflect the actual time and date.

 

Running the date command on the UNIX server returns the expected value every time so I'm not sure why Tcl is acting the way it is. Can someone provides some clues?

Robert M. Bartis&nbsp;
Stinger Quality Assurance
TEL: (908) 582-6566
EMAIL: alcatel-lucent.com">bartisalcatel-lucent.com

 

 # Define common logging function to be called for all levels
&nbsp;private method commonLog {lvl s} {
 &nbsp;if {[lsearch $lvls $lvl] < $lvlNum}
&nbsp; puts $s
 &nbsp;   ; &nbsp; &nbsp; &nbsp; &nbsp;  
 &nbsp;set ts [clock format [clock seconds]]
  ;set s "$ts:$name:$s"
  puts $fid "$s"
 ; 
&nbsp; 
 &nbsp;# Provide means to flush file buffer each time to ensure
&nbsp; # debug information does not get lost if required
  ;if {$flush == 1} {
 &nbsp; flush $fid
 ; &nbsp;flush stdout
&nbsp; }
 }

Robert M. Bartis&nbsp;
Stinger Quality Assurance
TEL: (908) 582-6566
EMAIL: alcatel-lucent.com">bartisalcatel-lucent.com

---

From: Andreas Kupries [mailto:andreaskactivestate.com]
Sent: Thursday, August 16, 2007 11:58 AM
To: Bartis, Robert M (Bob); activetcllistserv.ActiveState.com; RoTcl@yahoogroups.com; tcltk@yahoogroups.com
Subject: RE: Simple timestamp

First question coming to mind - Is this Tcl 8.4 or Tcl 8.5 ?

Second question: Are the results of 'clock seconds'&nbsp;also all over the place, or only the results from 'clock format' operating on them ?

 

--
 &nbsp;   ; &nbsp; Andreas Kupries <andreaskActiveState.com>
&nbsp;   ; &nbsp;  Developer http://www.ActiveState.com
&nbsp; &nbsp; &nbsp; &nbsp; Tel: +1 778-786-1122
 

-----Original Message-----
From: Bartis, Robert M (Bob) [mailto:activetcl-bounceslistserv.ActiveState.com]On Behalf Of Bartis, Robert M (Bob)
Sent: Wednesday, August 15, 2007 6:01 PM
To: activetcllistserv.ActiveState.com; RoTcl@yahoogroups.com; tcltk@yahoogroups.com
Subject: Simple timestamp

All

 

I have loaded the most current Tcl distribution from the ActiveState site down to a local UNIX server. The application includes a basic logging function which prefixes all messages sent to be logged with a timestamp.

 

e.g

proc log {

set ts [clock format [clock seconds]]

puts "$ts - $msg"

}

The problem I am having is the value returned from [clock format [clock seconds]] jumps all over the place. Both the time, day, month and year come back with inaccurate values (e.g. Thu Apr 04 14:24:38 CDT 1912).&nbsp; All value are valid, just do not reflect the actual time and date.

 

Running the date command on the UNIX server returns the expected value every time so I'm not sure why Tcl is acting the way it is. Can someone provides some clues?

Robert M. Bartis&nbsp;
Stinger Quality Assurance
TEL: (908) 582-6566
EMAIL: alcatel-lucent.com">bartisalcatel-lucent.com