Yeah, I just did some looking around -- and I can't find 'UEST' as a
time zone. We've got 'EST' (Eastern Standard Time, North America, UTC -
5) and 'EST' (Eastern Summer Time, Australia at UTC + 11, Eastern
Standard Time, Australia, UTC + 10) and 'U' (Uniform time zone, military
(US?) UTC - 8).
I'm going from this site:
http://www.timeanddate.com/library/abbreviations/timezones/
But the field IS the time-zone field on the headers from the *nix
systems. I wonder if we'll see 'UEDT' next year, since Indiana has
decided to get back into the "change the clock" game.
I'd still like to see the source . . .
Tom
-----Original Message-----
From: PAUL WILLIAMSON [mailto:user-b9fa55f5c833@xymon.invalid]
Sent: Wednesday, December 28, 2005 1:12 PM
To: user-ae9b8668bcde@xymon.invalid
Subject: RE: [hobbit] Anyone working on an NT client?
user-290ce4e24e19@xymon.invalid 12/28/05 12:01 PM >>>
On Wed, 2005-12-28 at 11:54 -0500, Kauffman, Tom wrote:
Well, among other things, I'd be a bit happier about the client
myself
if the company name weren't so prominently mis-spelled in the past
two
releases. I'm assuming that 'UEST' in this header is really
supposed to
be 'QUEST': Wed Dec 28 12:01:19 UEST 2005.
Isn't that a timezone?
Assumptions are a funny thing...
LOL, that is some funny ish...I seriously doubt they'd stick the
name of their company in the middle of the date. It's probably
referencing they are using Universal EST or something like that.
I've never heard of that, but I'm guessing that the UEST is not
because they misspelled Quest.
Paul