---- michael <cs@xxxxxxxxxxxxxxxxxxxxxxxxxxx> wrote: > On Wed, 2008-08-06 at 09:20 -0400, Todd Denniston wrote: > > michael wrote, On 08/06/2008 03:56 AM: > > > It seems my clock is losing time but yet I have 'enable Network Time > > > Protocol' enabled and set to a local time machine. If I > > > > by "a local time machine" do you mean: > > server 127.127.1.0 > > ??? > > > > or > > server 130.88.200.6 burst > > restrict 130.88.200.6 mask 255.255.255.255 nomodify notrap noquery > > ??? > > > I didn't mean 127.127.1.0 (no idea what that means...) and yes I did > mean 130.88.200.6 although I've no idea what those server/restrict cmds > are about > > > 127.127.1.0 is only *sort of* reliable once it has been disciplined, i.e., a > > drift file built up for a few days. > > > > > > > > sudo /etc/init.d/ntpd stop > > > sudo /usr/sbin/ntpdate 130.88.200.6 > > > > > > then it resets it to the correct time, so how come it's losing time? > > > > > > > start ntpd, wait ~15 minutes, then run > > /usr/sbin/ntpq -p > > and send us the results. > > i.e., to little information so far. > > okay, restarted ntpd from cmd line, waiting 15 mins and here's ntpq =p > gives: > mkb@veri:/var/log$ sudo /usr/sbin/ntpq -p > Password: > remote refid st t when poll reach delay offset > jitter > ============================================================================== > utserv.mcc.ac.u 193.62.22.98 2 u 14 64 377 0.303 369608. > 3831.40 > > but it's still out: > > mkb@veri:/var/log$ date > Wed Aug 6 16:41:41 BST 2008 > > mkb@veri:/var/log$ ssh michael@ratty date > Wed Aug 6 16:47:57 BST 2008 ntp is designed to make small changes to your computer's time so that any application that relies on the continuous passage of time doesn't get freaked out by sudden jumps. Keep running that ntpq command every 5 mins or so and as long as the offset is getting smaller, everything is OK. One other thing you might want to consider is to have more than one peer. If your main peer goes down or the network between you and the peer gets too slow, ntp will automatically swap to the next best choice. If your time eventually does get synchronized, but everytime you power up the computer it is wrong again, then you probably need to replace the computer's battery. Steve -- fedora-list mailing list fedora-list@xxxxxxxxxx To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
