> Otto Moerbeek wrote:
>
> > ntpd is never going to be able to correct these large offets within
> > reasonable
> > time. It was designed to adjust clocks that have offsets of a couple of
> > minutes. Seeing the messages in syslog clear indicates you have some work to
> > do. So i like them to s
On Tue, Sep 18, 2012 at 8:12 AM, Christian Weisgerber
wrote:
> Otto Moerbeek wrote:
>
>> ntpd is never going to be able to correct these large offets within
>> reasonable
>> time. It was designed to adjust clocks that have offsets of a couple of
>> minutes. Seeing the messages in syslog clear in
Otto Moerbeek wrote:
> ntpd is never going to be able to correct these large offets within reasonable
> time. It was designed to adjust clocks that have offsets of a couple of
> minutes. Seeing the messages in syslog clear indicates you have some work to
> do. So i like them to stay.
xntpd exits
ntpd is never going to be able to correct these large offets within reasonable
time. It was designed to adjust clocks that have offsets of a couple of
minutes. Seeing the messages in syslog clear indicates you have some work to
do. So i like them to stay.
-Otto
Op 17 sep. 2012 om 09:16 heeft Ma
Hello,
After running ntpd for the first time on a machine with a bad clock, I
got the following in syslog:
ntpd[24277]: adjusting local clock by 369307689.625505s
ntpd[24277]: adjtime failed: Invalid argument
I think adjtime limits its argument to a maximum value. Apparently on
Unix this
