Date: Sat, 07 Sep 2019 07:53:25 -0000 From: Harlan Stenn <stenn@nwtime.org> To: Cy Schubert <Cy.Schubert@cschubert.com> Cc: Vladimir Zakharov <zakharov.vv@gmail.com>, Konstantin Belousov <kostikbel@gmail.com>, freebsd-current@freebsd.org Subject: Re: ntpd segfaults on start Message-ID: <156d1e7c-0dbb-8707-90b3-13ae97c87449@nwtime.org> In-Reply-To: <201909062356.x86NuKdk003780@slippy.cwsent.com> References: <20190905061251.rrip6635ebbfimsv@vzakharov> <20190905063354.qxecqjkafikdtdyq@vzakharov> <201909051307.x85D7MGs034053@slippy.cwsent.com> <20190905142817.GB2559@kib.kiev.ua> <201909060355.x863tRhP089169@slippy.cwsent.com> <201909060639.x866dJ7f090176@slippy.cwsent.com> <201909062356.x86NuKdk003780@slippy.cwsent.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Cy, On 9/6/2019 4:56 PM, Cy Schubert wrote: > ... > > For those who enable ASLR, a better workaround is, to add this to your > ntp.conf: > > rlimit memlock 64 > > Until a more precise default is determined. Should I change the default value for FreeBSD-12 to be 64 for now? I can get this change in place for the upcoming ntp-4.2.8p14 release, and we can change it later if needed. -- Harlan Stenn, Network Time Foundation http://nwtime.org - be a Member!
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?156d1e7c-0dbb-8707-90b3-13ae97c87449>