time stamped on threads

Hi Leonard. it looks to me that the clock on your computer is about ten minutes early.I realize that you are in a different time zone but that means two hours not two hours and ten minutes. Not important I guess and I apologise for being picky. JUst one of my personal things. I make some effort to keep my watch within a second of the right time. and my computer gets it from some satelite I guess. Thanks for the forum and the great service on supplies. Keith V

> Hi Leonard. it looks to me that the clock on your computer
>is about ten minutes early.I realize that you are in a
>different time zone but that means two hours not two hours
>and ten minutes. Not important I guess and I apologise for
>being picky. JUst one of my personal things. I make some
>effort to keep my watch within a second of the right time.
>and my computer gets it from some satelite I guess. Thanks
>for the forum and the great service on supplies. Keith V

Keith;

This is a function of the ISP not keeping the server's clock synched with time server. Leonard and I have pointed it out to the ISP a number of times, but to no avail.

Compared to some of the other turmoil we have been through, ten minutes delta between SSW and UST is minor.

V/r

Now that I am back from the Nats, I will send them a "ticket". I am in Illinois, the server is in Texas. Makes it a little difficult to go over there in person. They usually respond when I tell them, but eventually it will drift off again. They need atom time to keep the server's time clock syntronized. Most people don't worry about a time clock on a server, so it is probably not a high priority item for them.

>Most people don't worry about a
>time clock on a server, so it is probably not a high
>priority item for them.

Not a very good excuse on the part of your ISP, Len. Surely they know about Network Time protocol (ntpd/ntpupdate). Send them to http://www.eecis.udel.edu/~mills/ntp/clock2a.html if they don't. Really, this is Sysadmin 101 stuff.