Date: Wed, 14 Oct 2009 19:01:45 -0400 (EDT) From: Chris Hill <chris@monochrome.org> To: Jacques Henry <caramba696@googlemail.com> Cc: freebsd-questions@freebsd.org Subject: Re: NTP Client synchronization with a Windows 2003/2008 Message-ID: <alpine.BSF.2.00.0910141852140.5763@tripel.monochrome.org> In-Reply-To: <2345d18f0910140904v3e2e9f37hbaabc05cb561a19d@mail.gmail.com> References: <2345d18f0910130813j6a2bbde0sec59647f44d43585@mail.gmail.com> <2345d18f0910130921g17b8d9fdy8fdb99bd5a0e8cf4@mail.gmail.com> <4AD4AE89.6010802@radel.com> <200910140902.27825.j.mckeown@ru.ac.za> <2345d18f0910140904v3e2e9f37hbaabc05cb561a19d@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 14 Oct 2009, Jacques Henry wrote: >>> The 19 minutes between when I sent my suggestions and you responded is >>> hardly enough time to see if ntpd was slewing the time. Slewing 587 >>> seconds takes days. >> > > The thing is that ntpd is not slewing the time at all, even after several > hours!! If I may pipe up... Can you not set the clock manually, then let ntpd take it from there? Seems like your clock would become synced a lot faster if it started out "close". Sorry if I'm being naive, but this seemed like the obvious thing to do. -- Chris Hill chris@monochrome.org ** [ Busy Expunging <|> ]
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?alpine.BSF.2.00.0910141852140.5763>