So is this expected and intended consequence, bug or still unfinished part of the project? Just curious (it runs on FreeBSD-current, latest CentOS, NetBSD-8). On Wed, 26 Sep 2018 at 17:33, Christos Zoulas <chris...@astron.com> wrote: > > In article > <CAG0OUxgnv9uYDBZMeYm_WTg8wPm=bvvr5a67bozgvjekw9z...@mail.gmail.com>, > Chavdar Ivanov <ci4...@gmail.com> wrote: > >-=-=-=-=-=- > > > >Hi, > > > >On amd64 -current from yesterday the latest lsof returns immediately if > >invoked by non-root user. I am sure it worked a few weeks ago. It works ok > >for the root. > > > >ktruss /usr/pkg/sbin/lsof > > > >returns only: > > > >fcntl(0x4, 0x3, 0) = 4194305 > >emul(netbsd) > >fcntl(0x4, 0x4, 0x400001) = 0 > > > >Seeing it is installed setgid kmem, I added myself to the group, no effect. > > > >lsof was rebuilt once more just in case. > > > >Is this some new security measure or a fallout? > > I think this is part of maxv@ changes to hide pointers from userland. > > christos >
-- ----
