Re: [foxboro] DST

Ok, but it's not Mosaic's fault, it's I/A's fault.  Thanks for clearing
that up.

Tim Lowell
Control Systems Engineer
ConocoPhillips Trainer Refinery
(610) 364-8362
tim.c.lowell@xxxxxxxxxxxxxxxxxx


-----Original Message-----
From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx]
On Behalf Of ajohnso7@xxxxxxxxxxxxxx
Sent: Tuesday, October 26, 2004 1:56 PM
To: foxboro@xxxxxxxxxxxxx
Subject: Re: [foxboro] DST

Corey is correct. The problem is that we set time back and Mosaic
doesn't like it.

In V8 of the I/A Series, we do not change the system time only the
timezone. So the problem goes away (once we have Solaris on V8 anyway).


AJ

PS. Sprint is blacklisted and so I have to use another e-mail address. I
know I'm going to regret putting this address on the list. Sigh...

----- Original Message -----
From: Corey R Clingo <clingoc@xxxxxxxxxxxxx>
Date: Tuesday, October 26, 2004 7:39 pm
Subject: Re: [foxboro] DST

> I think it is *I/A* version 8, not FV version 8, that will have=20
> "time done=20
> right".  It will utilize the Unix time zone facility properly=20
> (it's, um,=20
> about time...), so that the internal (GMT) system clock does not=20
> change=20
> when the time zone changes (only the translation to local time is=20
> affected).  You won't have to set the clock forward or back.  It=20
> is the=20
> misuse of the Unix time facility in current I/A versions, which=20
> inexplicably wasn't fixed during the transition from Venix to=20
> Solaris,=20
> that causes the current problems with DST changes.
> I also think it is Motif that does not update events, not X, as DM=20
> and=20
> other X apps do not seem to have difficulties when the clock is=20
> set back.=20
> Since I don't envision our getting I/A version 8.1 anytime real=20
> soon, we=20
> cooked up a script to set the time back, restart all the FVs, and=20
> stop the=20
> legacy historians for an hour to make this crap as painless as=20
> possible.
> Corey Clingo
> BASF Corp.
>=20
>=20
>=20
>=20
>=20
>=20
> "Lowell, Tim:" <Tim.C.Lowell@xxxxxxxxxxxxxxxxxx>
> Sent by: foxboro-bounce@xxxxxxxxxxxxx
> 10/26/2004 10:51 AM
> Please respond to foxboro
>=20
>              To:  foxboro=20
>              cc:=20
>         Subject:       Re: [foxboro] DST
>=20
>=20
>=20
>=20
>=20
>=20
> Oh, boy.  Have you opened up a can of worms, Sascha.
>=20
> I love how they blame the X-server, and then say that FoxView v8=20
> will =3D
> have "time done right".  Hmm, if it's the X-server's fault, and=20
> FoxView =3D
> v8 runs on an X-server the same as FoxView 99.2.1, how could you =3D
> possibly fix it to make it "done right"?
>=20
> Sorry, but I'm not exactly looking forward to coming in this=20
> Sunday, so =3D
> cut me some slack.
>=20
> Tim Lowell
> Control Systems Engineer
> ConocoPhillips Trainer Refinery
> (610) 364-8362
> tim.c.lowell@xxxxxxxxxxxxxxxxxx
>=20
>=20
> -----Original Message-----
> From: foxboro-bounce@xxxxxxxxxxxxx [foxboro-bounce@xxxxxxxxxxxxx] =3D
> On Behalf Of Sascha Wildner
> Sent: Tuesday, October 26, 2004 11:26 AM
> To: Foxboro DCS Mail List
> Subject: [foxboro] DST
>=20
> Quoting from the Foxboro Customer Advisory:
>=20
> -------- Original Message --------
> [...]
> After the clock is set back in time, all the screens using FoxView=20
> will=3D20lock up and wait for the current date/time to catch up to=20
> the latest=3D20
> time the FoxView display manager saw before updating any points =
or=3D20
> executing any operator commands. This Solaris FoxView issue is=20
> related=3D20to the way that X-Window handles time stamps on event=20
> messages. Each=3D20
> X-Window event is time stamped, and the X-Server makes sure that=20
> events=3D20are not delivered before the "current" time. This is a=20
> behavior of Motif =3D
>=20
> applications such as FoxView and several Batch products that is=20
> only=3D20found on the Solaris platforms.
> [...]
> ----------------------------------
>=20
> I mean, is this really the X server's fault? Why does my own box=20
> running =3D
>=20
> under X not lock up for an hour upon DST changing? Isn't the time=20
> you=3D20get when you type 'date' only a translation of the internal=20
> time=3D20(seconds since Jan. 1, 1970) according to time zone rules?
>=20
> I just want to understand this issue, any insight is appreciated.
>=20
> Regards,
>=20
> --=3D20
> Sascha Wildner
> erpicon Software Development GmbH
> Neusser Str. 724-726
> 50737 K=3DF6ln
> Germany
>=20
> Phone: +49 221 9746069
> Fax:   +49 221 9746099
> eMail: swildner@xxxxxxxxxx
>=20
> =3D20
> =3D20
>
_______________________________________________________________________
> This mailing list is neither sponsored nor endorsed by Invensys=20
> ProcessSystems (formerly The Foxboro Company). Use the info you=20
> obtain here at
> your own risks. Read=20
> http://www.thecassandraproject.org/disclaimer.html=3D20
> foxboro mailing list:            =20
> http://www.freelists.org/list/foxboroto subscribe:         =3D
> foxboro-request@xxxxxxxxxxxxx?subject=3D3Djoin
> to unsubscribe:      =3D
> foxboro-request@xxxxxxxxxxxxx?subject=3D3Dleave
> =3D20
>=20
>=20
>
_______________________________________________________________________
> This mailing list is neither sponsored nor endorsed by Invensys=20
> ProcessSystems (formerly The Foxboro Company). Use the info you=20
> obtain here at
> your own risks. Read=20
> http://www.thecassandraproject.org/disclaimer.html
> foxboro mailing list:            =20
> http://www.freelists.org/list/foxboroto subscribe:         foxboro-
> request@xxxxxxxxxxxxx?subject=3Djointo unsubscribe:      foxboro-
> request@xxxxxxxxxxxxx?subject=3Dleave
>=20
>=20
>=20
>=20
>=20
>=20
>=20
>
_______________________________________________________________________
> This mailing list is neither sponsored nor endorsed by Invensys=20
> ProcessSystems (formerly The Foxboro Company). Use the info you=20
> obtain here at
> your own risks. Read=20
> http://www.thecassandraproject.org/disclaimer.html=20
> foxboro mailing list:            =20
> http://www.freelists.org/list/foxboroto subscribe:         foxboro-
> request@xxxxxxxxxxxxx?subject=3Djointo unsubscribe:      foxboro-
> request@xxxxxxxxxxxxx?subject=3Dleave=20
>=20

=20
=20
_______________________________________________________________________
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
=20
foxboro mailing list:             http://www.freelists.org/list/foxboro
to subscribe:         =
mailto:foxboro-request@xxxxxxxxxxxxx?subject=3Djoin
to unsubscribe:      =
mailto:foxboro-request@xxxxxxxxxxxxx?subject=3Dleave
=20
 
 
_______________________________________________________________________
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: