On Sat, Sep 07, 2019 at 12:53:19AM -0700, Harlan Stenn wrote:
> 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.
>
In message <20190907075619.gg2...@kib.kiev.ua>, Konstantin Belousov writes:
> On Sat, Sep 07, 2019 at 12:53:19AM -0700, Harlan Stenn wrote:
> > 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
> > > n
I got the following panic this AM during a poudriere run.
r351627 is the revision I'm at.
Core *IS* available.
Ideas?
Unread portion of the kernel message buffer:
VNASSERT failed
0xf809e6335960: tag tmpfs, type VREG
usecount 1, writecount 0, refcount 2
flags (VI_ACTIVE)
v_obj
On Sat, Sep 07, 2019 at 08:49:10AM -0500, Larry Rosenman wrote:
> I got the following panic this AM during a poudriere run.
>
> r351627 is the revision I'm at.
>
> Core *IS* available.
>
> Ideas?
It highly suspect that is should be fixed by
https://reviews.freebsd.org/D21560.
Slightly amused tha
On Sat, Sep 07, 2019 at 06:09:16AM -0700, Cy Schubert wrote:
> In message <20190907075619.gg2...@kib.kiev.ua>, Konstantin Belousov writes:
> > On Sat, Sep 07, 2019 at 12:53:19AM -0700, Harlan Stenn wrote:
> > > Cy,
> > >
> > > On 9/6/2019 4:56 PM, Cy Schubert wrote:
> > > > ...
> > > >
> > > > Fo
In message <20190907153226.gi2...@kib.kiev.ua>, Konstantin Belousov writes:
> On Sat, Sep 07, 2019 at 06:09:16AM -0700, Cy Schubert wrote:
> > In message <20190907075619.gg2...@kib.kiev.ua>, Konstantin Belousov writes:
> > > On Sat, Sep 07, 2019 at 12:53:19AM -0700, Harlan Stenn wrote:
> > > > Cy,
On Sat, Sep 07, 2019 at 08:45:21AM -0700, Cy Schubert wrote:
> I've been able to set the memlock rlimit as low as 20 MB. The issue is
> letting it default to 0 which allows ntp to mlockall() anything it wants.
> ntpd on my sandbox is currently using 18 MB.
Default stack size on amd64 is 512M, an
In message <20190907161749.gj2...@kib.kiev.ua>, Konstantin Belousov writes:
> On Sat, Sep 07, 2019 at 08:45:21AM -0700, Cy Schubert wrote:
> > I've been able to set the memlock rlimit as low as 20 MB. The issue is
> > letting it default to 0 which allows ntp to mlockall() anything it wants.
> > n
