On Tue, Jun 28, 2016 at 11:39:16PM -0700, Hal Murray wrote: > > matthew.sel...@twosigma.com said: > > "rlimit memlock 0" using Classic causes ntpd to died after 3 minutes with > > this error 2016-06-29T00:13:21.903+00:00 host.example.com ntpd[27206]: > > libgcc_s.so.1 must be installed for pthread_cancel to work > > What version of Classic are you running? I though they had fixed that.
This lab system happens to be running 4.2.7.0p368 Super-old, I know. I'll upgrade it over the weekend. > > I've attached 15 minute graphs for "rlimit memlock -1" and "rlimit memlock > > 128" using Classic. Locking memory seems to result in more stable graphs > > over the time period that I was able to collect quickly. > > What are you plotting? Y-axis is offset as measured by ntpq -p in microseconds. X-axis is time. And the 3 lines represent 3 different remote refclocks that my ntp client is pointing at. Cheers, -Matt _______________________________________________ devel mailing list devel@ntpsec.org http://lists.ntpsec.org/mailman/listinfo/devel
