Re: lsof outputs nothing
Hi.
On Sun, May 17, 2020 at 11:51:00AM -0500, David Wright wrote:
> On Sun 17 May 2020 at 09:34:42 (-0400), Gene Heskett wrote:
> > On Sunday 17 May 2020 06:25:20 Reco wrote:
> > > On Sun, May 17, 2020 at 01:04:23PM +0300, aprekates wrote:
> > > > In Buster lsof wont report anything
> > > >
> > > > $ sudo lsof
> > > > lsof: WARNING: can't stat() fuse file system /run/user/1000/doc
> > > > Output information may be incomplete.
> > >
> > > Most likely this fuse filesystem was not mounted with "allow_other"
> > > option. Its contents is inaccessble to root, hence lsof behaviour is
> > > expected.
>
> So is this a case where some helpful software, like a DE, has unset that
> option for the user?
>
> I seem to get it set as the default:
>
> I set: ro,nofail,umask=022,uid=1000,gid=1000
> I see: ro,relatime,user_id=0,group_id=0,default_permissions,allow_other,blksize=4096
Every time I use sshfs or archivemount I have to specify allow_other
explicitly, or it's not there.
> That's mounting ntfs filesystems from fstab with AIUI fuse (fuseblk filetype).
This may be specific for that particular fuse filesystem, or fuseblk.
> Open files on these filesystems are seen in the lsof output by root
> and whoever has the files open, as I had kind of expected.
If root can browse the filesystem then lsof with root euid can do it
too.
Reco
Reply to: