© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
bbfa235
(Get the code!)
I've just set up a machine with FreeBSD 10.2-RELEASE from scratch, and I don't see any problem with the version of ntpd shipped with FreeBSD.
It's labelled "4.2.8p3-a", but I don't know what the "-a" stands for.
The only problem I encountered is that I had to remove "nopeer" from the "restrict" lines in the shipped ntp.conf file if I wanted to use the "pool" directive, since otherwise no pool servers were added. However, the comments in bug 2152 say this is OK.
Digging through bugzilla I found a few issues where ntpd didn't work correctly due to memory restrictions:
Bug 2362 - mlockall() breaks DNS resolution when using the "files" service in nsswitch.conf
http://
Bug 2643 - Server crash with pool directive
http://
Bug 2817 - Stop locking ntpd into memory by default
http://
For me it smells like all this is somehow related. Can you try if the problem still persists if you add an "rlimit memlock 128" line (or even a higher number) to ntp.conf?
If I find some time I'll try to build ntp-dev on my FreeBSD machine and see if I can duplicate the problem.
On the other hand, Hal reported on the hackers@ list that he also saw this on Fedora 22. I've also installed that Linux version a few days ago and played a bit with it, but didn't encounter any problems with the shipped ntpd, either.