[foxboro] DST

Quoting from the Foxboro Customer Advisory:

-------- Original Message --------
[...]
After the clock is set back in time, all the screens using FoxView will 
lock up and wait for the current date/time to catch up to the latest 
time the FoxView display manager saw before updating any points or 
executing any operator commands. This Solaris FoxView issue is related 
to the way that X-Window handles time stamps on event messages. Each 
X-Window event is time stamped, and the X-Server makes sure that events 
are not delivered before the "current" time. This is a behavior of Motif 
applications such as FoxView and several Batch products that is only 
found on the Solaris platforms.
[...]
----------------------------------

I mean, is this really the X server's fault? Why does my own box running 
under X not lock up for an hour upon DST changing? Isn't the time you 
get when you type 'date' only a translation of the internal time 
(seconds since Jan. 1, 1970) according to time zone rules?

I just want to understand this issue, any insight is appreciated.

Regards,

-- 
Sascha Wildner
erpicon Software Development GmbH
Neusser Str. 724-726
50737 Köln
Germany

Phone: +49 221 9746069
Fax:   +49 221 9746099
eMail: swildner@xxxxxxxxxx

 
 
_______________________________________________________________________
This mailing list is neither sponsored nor endorsed by Invensys Process
Systems (formerly The Foxboro Company). Use the info you obtain here at
your own risks. Read http://www.thecassandraproject.org/disclaimer.html
 
foxboro mailing list:             http://www.freelists.org/list/foxboro
to subscribe:         mailto:foxboro-request@xxxxxxxxxxxxx?subject=join
to unsubscribe:      mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave

Other related posts: