From: Guy Harris <guy@netapp.com> Date: Tue, 15 Feb 2000 14:46:02 -0800 (PST)
zdump -v outputs TZ's value.
On some platforms. On others, not: tooting$ uname -sr SunOS 5.5.1 tooting$ zdump tooting$ zdump -v Sorry, my comment was too terse. I should have written that `zdump -v ZONE' outputs ZONE, where ZONE is the value of the TZ environment variable. That is how the latest zdump internally implements the translation from the string 'ZONE' to a series of clock transitions. E.g.: 15-red.twinsun.com $ uname -sr SunOS 5.5.1 16-red.twinsun.com $ zdump -v US/Pacific US/Pacific Tue Feb 15 17:00:55 2000 PST US/Pacific Fri Dec 13 20:45:52 1901 GMT = Fri Dec 13 13:45:52 1901 isdst=0 ... SunOS 5.5.1 is running an old version of zdump. The latest tzcode zdump outputs something a bit different, but `zdump -v US/Pacific' still outputs `US/Pacific' on each line. ecco*> version NetApp Release 5.3.4R3: Thu Jan 27 12:08:07 PST 2000 ... ecco*> timezone Current time zone is US/Pacific Good point. In other words, even if your system has no notion of the "TZ environment variable", you print the value that you'd use for TZ if you were running tzcode.