ntpd

[Jon Radel]

On 10/22/16 6:23 PM, Stari Karp wrote:

> Oct 22 18:10:49 osolemio ntpd[926]: ntpd 4.2.8p8-a (1): Starting
> Oct 22 18:10:49 osolemio ntpd[927]: format error frequency file
> /var/db/ntpd.drift

What happens if you move the ntpd.drift file aside, and restart ntpd?
It should create a new file, although you may have to wait on order of
an hour for that to happen.  Comparing the format of the files might
make clearer what went wrong.

Possibly, you've simply ended up with an empty drift file and need to
wait long enough for it to be populated with real data.

In any case, you don't need a ntpd.drift when you start, it simply
speeds up the process of ntpd determining the clock drift for your
specific hardware upon subsequent reboots.  If it breaks upon major
upgrade, you can simply delete the file and have ntpd recreate it,
though I've never heard of an upgrade breaking the file.  Usually this
is due to people manually creating the file and/or having directory
write permissions that keep ntpd from writing a file with real data.

Is this a fresh install of 11.0 p1?  You really don't give us much to go on.


-- 
--Jon Radel
jon at radel.com

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 3890 bytes
Desc: S/MIME Cryptographic Signature
URL: <http://lists.freebsd.org/pipermail/freebsd-questions/attachments/20161022/7bf4ccaf/attachment.bin>