Michael Meier writes: > > See http://bugs.ntp.org/2471 - this feels like the rlimit issue to me. > > Try adding: > > rlimit memlock 128 > > to your ntp.conf file. This is an issue with glibc and friends, and it > > sucks to make the amount of memory locked for ntpd to be too big, and if > > it's not big enough then ntpd will crash. The default value of 32 > > megabytes is enough for most everybody. > > Better yet, set "rlimit memlock 0" to disable the behaviour of ntpd > trying to lock itself into memory altogether. > I have yet to find a limit that doesn't crash on a very busy server > after $random_timespan. And it's also a waste of your memory, because it > forbids the OS to simply swap out things that are never used.
I like this idea best of all. I realize now I've been focusing on getting the "right" number because I *assumed* that folks were complaining about this because they *wanted* to lock ntpd in memory. I'm going to start a discusison about this on questions@. Thanks, Michael! H _______________________________________________ pool mailing list [email protected] http://lists.ntp.org/listinfo/pool
