<HTML><BODY style="word-wrap: break-word; -khtml-nbsp-mode: space; -khtml-line-break: after-white-space; "><BR><DIV><DIV>On Mar 11, 2007, at 9:38 AM, Larry K wrote:</DIV><BR class="Apple-interchange-newline"><BLOCKQUOTE type="cite">Today, I checked and found that my myth box still has EST, not EDT. I use ntp, so I didn't expect a problem with this. My /etc/ntp.conf shows that I am using these time servers:<BR><BR># --- OUR TIMESERVERS -----<BR> server <A href="http://80.53.57.158">80.53.57.158</A><BR>server <A href="http://192.117.105.69">192.117.105.69</A><BR>server <A href="http://64.5.1.129">64.5.1.129</A><BR><BR>My windows machine uses a time server as well ( Rocket.time), and it too is wrong. My primary server in this case is:<BR><BR><A href="http://time-a.nist.gov">time-a.nist.gov</A>.<BR><BR></BLOCKQUOTE>This has nothing to do with your time servers, it has to do with your timezone data.<BR></DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV>For Linux you have to have the correct tzdata, the exact method of updating depends on your distro.</DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV>For Windows recent updates are supposed to have corrected that.</DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV>But the timeserver just gives you UCT, the correction to local zones is done by your OS. </DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV>Some BIOS clocks try and automatically adjust for DST, they will almost certainly be wrong today but once the OS is up it should correct that.</DIV><BR></BODY></HTML>