Hi!
Juergen> [...] Consider the following example:
Juergen> $ TZ=UTC ./scli -c "show system info" xxxx | grep Time Juergen> Current Time: 2002-05-02 12:04:05 +02:00 Juergen> Agent Boot Time: 2002-04-20 15:29:15 +00:00 Juergen> System Boot Time: 2002-01-22 09:41:39 +00:00
Juergen> Obviously, the boot time stamps honor the local time zone (since they Juergen> were computed by scli from TimeTicks values) while the current time is Juergen> displayed in the time zone of the device. Perhaps it would be more Juergen> intuitive to get all time values in the local time zone - allowing Juergen> people to use TZ to control the actual time zone for all time stamps.
Juergen> Comments?
In general, I agree. ;-) But I could also imagine situations, where the agent's timezone could be useful, e.g. when you setup a Schedule-MIB entry to launch a backup process at midnight (agent time). I suggest three steps:
(1) Do print all time stamps according to a common timezone, preferably the scli's local timezone (by default). (2) Append a clearifying string to printed timestamps, e.g.: Current Time: 2002-05-02 12:04:05 +00:00 (console time) (3) Introduce a configurable variable (set scli timezone <console|agent>) and print timestamps accordingly, e.g.: Current Time: 2002-05-02 12:04:05 +02:00 (agent time)
-frank