Hello,
I am using a System based on FreeBSD 6.3.
On this System an automatically generated ntpd.conf file is generated in
order to synchronize the System clock with a NTP Server. I want to use a
Windows 2003 or 2008 Server to act as the NTP Server. On the Windows System
the NTP Server (Windows Tim
Hello,
I am using a System based on FreeBSD 6.3.
On this System an automatically generated ntpd.conf file is generated in
order to synchronize the System clock with a NTP Server. I want to use a
Windows 2003 or 2008 Server to act as the NTP Server. On the Windows System
the NTP Server (Windows Tim
>
> ntpd wont resync if the time difference is to big, as it assumes something
> is wrong as you would have set the system clock roughly correct. To fix stop
> ntpd, then do an ntpdate against the server. This should set the time. Now
> run ntpd again
>
> also set the following variables to a serve
> > 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!!
> > Are you sure that -x in there, tell
>
> 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.
>
>
Don't apologize! Any input is valuable! B
