-={ Wed Nov  5 10:34:16 PST 2014 }=-

Hey All!

I promise that this is the last message from me about this issue.

Now that standard time is officially here as of Nov. 2 I see that a node in my
timezone is back to up to the second accuracy with the node here as evidenced
by a cut n' paste from binkd.log;

- 05 Nov 17:03:04 [16745] TIME 2014/11/05 09:03:04 -8:00

The datetime stamp on the left is in UTC and a poll from the Guy Robot point
will serve as evidence to that;

- 04 Nov 23:38:52 [7146] TIME Tue,  4 Nov 2014 23:38:52 +0000

Note that all three are in agreement to the second as well as the '+' character
to the UTC offset for UTC.  Also it should be mentioned that coreutils' date
had no issue converting the remote's datetime stamp to UTC as shown below;

fidonet@zoltan [ ~ ]$ date --date="2014/11/05 09:03:04 -8:00"
Wed Nov  5 17:03:04 UTC 2014

I won't bother converting the point or node's datetime stamp as they are both
UTC and as shown are in agreement up to the second.  Also worthy of mention is
that a completly independent node to the ones above, as well as a different
timezone, also agrees up to the second about what time it *really* is, not to
mention the trusted timeservers completly independent of Fidonet (ntpd based).

I am taking the liberty of dropping TZUTC as it is most definetly in error
despite it having zero influence over anything significance.  I honestly
checked everywhere I could to make sure it is indeed a complete waste of bytes.

Life is good,
Maurice

... Don't cry for me I have vi.
--- GNU bash, version 4.3.30(1)-release (x86_64-atom-linux-gnu)