<x-html>
<br><font size=2><tt>Here in Indiana we avoid the issue by never shifting any of
our</tt></font>
<br><font size=2><tt>clocks. Like Foxboro, corn, beans and livestock are
very</tt></font>
<br><font size=2><tt>sensitive to shifts in time.</tt></font>
<br>
<br><font size=2><tt>I do have another time question...</tt></font>
<br>
<br><font size=2><tt>Has anyone either modified the xntp daemon for Solaris to
serve</tt></font>
<br><font size=2><tt>the Foxboro time to PCs? Or, has anyone modified the client
ntp</tt></font>
<br><font size=2><tt>software to work with a Foxboro/GMT time server? If you
simply</tt></font>
<br><font size=2><tt>use the server and client software without modification all
your</tt></font>
<br><font size=2><tt>machines show time as assuming the server is at GMT. If you
set</tt></font>
<br><font size=2><tt>PCs to GMT it creates problems for email and other software
such</tt></font>
<br><font size=2><tt>as Aspen Tech client software. Ideally, I'd like to have
a</tt></font>
<br><font size=2><tt>modified ntp server on an AW51, that would allow me to specify
a</tt></font>
<br><font size=2><tt>TZ shift to account for Foxboro preference of TZ=0. This
would</tt></font>
<br><font size=2><tt>allow our processing areas to synchronize PC clocks so
that</tt></font>
<br><font size=2><tt>events recorded on all protocols can use a consistent
timestamp.</tt></font>
<br><font size=2><tt>provided by the DCS.</tt></font>
<br>
<br><font size=2><tt>It's also very possible that I simply don't understand all
the</tt></font>
<br><font size=2><tt>available options, and the ntp software can be configured
to</tt></font>
<br><font size=2><tt>function the way I desire.</tt></font>
<br>
<br><font size=2><tt>Thanks in advance for any help you can provide.</tt></font>
<br>
<br><font size=2><tt>Jim Murphy</tt></font>
<br><font size=2 face="Courier New">==========<br>
Senior Process Control Engineer<br>
Eli Lilly and Company<br>
Phone: (317) 276-6859<br>
Email: [EMAIL PROTECTED]</font></x-html>
