>
> 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
2009/10/15 Chris Hill
> 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 th
On Wednesday 14 October 2009 18:04:41 Jacques Henry wrote:
> > Alternatively, from the commandline try
> >
> > ntpd -g -q -c /etc/ntp.conf
> >
> > The -g flag allows ntpd to set the clock once regardless of the offset
> > and the -q causes it to quit after setting the time.
>
> I tried this comman
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 m
> > 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
On Tuesday 13 October 2009 18:44:57 Jon Radel wrote:
> Jacques Henry wrote:
> > I commented the commands involved and nothing changed... (with only 10
> > minutes of time difference)
>
> The 19 minutes between when I sent my suggestions and you responded is
> hardly enough time to see if ntpd was s
Jacques Henry wrote:
I commented the commands involved and nothing changed... (with only 10
minutes of time difference)
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.
I even
>
> 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
2009/10/13 Jacques Henry
> 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 Wind
Jacques Henry wrote:
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
On Tue, 13 Oct 2009 17:13:16 +0200
Jacques Henry (caramba...@googlemail.com) replied:
>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 20
11 matches
Mail list logo
