On 2015-10-21T16:23:41-0700, [email protected] wrote: > Back in February, when I upgraded to 4.2.8p2, I *had* to add "rlimit memlock > 0" to ntp.conf in order to get them to even run. Today I upgraded several > 4.2.8p2 servers running on Centos 7 to 4.2.8p4. They immediately ran out of > memory and stopped seconds after starting. So now in 4.2.8p4, I've had to > remove it to prevent out of memory crashes. Servers have 512-1024MB RAM and > does nothing else but NTP.
Same thing happened to me when I upgraded from 4.3.59 to 4.3.76 or 4.2.8p4. I mentioned this on IRC (#ntp on freenode), and Harlan replied that something changed, and now a memlock value of -1 means "don't lock" and 0 means "lock whatever we need". My ntpds have been stable for several hours now with -1. -- Kenyon Ralph
signature.asc
Description: Digital signature
_______________________________________________ pool mailing list [email protected] http://lists.ntp.org/listinfo/pool
