06 Oct 15 09:49, you wrote to Maurice Kinal:

 MK>> which is that the uplink's utc offset is wrong, not that it really
 MK>> matters any.  Despite it advertizing -0800 (should be -0700) it gets
 MK>> the correct time once adjusted but will be off an hour once it REALLY
 MK>> is -0800 which happens on Sunday 1 November 2015 2am local time. Then
 MK>> it will be flying the correct offset but the wrong time.

 WV> Your almost right. It advertises -0500 but because of DST it should be
 WV> -0400. ;)

that happens because in all cases i'm aware of, the operator has to flip the
switch... my main system uses an environment variable for this information... i
wrote a tool which automatically adjusts the value in the environment variable
when DST turns on and off... some systems require a reboot for the change to
take effect because of where the information is stored in environment variables
and whether they can be changed from a shell or not... if i had to guess, i'd
guess that janis simply forgot to adjust when the switch took place last
time...

)\/(ark

... Battle Creek makes cereal terminals.
---