Re: df shouldn't list mount points that it can't access

[n0dalus]

On 10/11/05, n0dalus <address@hidden> wrote:
> On 10/11/05, Paul Eggert <address@hidden> wrote:
> > n0dalus <address@hidden> writes:
> >
> > > In this case the mount point it can't access is part of a chroot'ed bind.
> > > In my opinion it should just quietly ignore that mount point.
> >
> > Thanks for reporting this.  Does the following patch fix your problem?
> >
> > http://lists.gnu.org/archive/html/bug-coreutils/2005-10/msg00048.html
> >
>
> Hi Paul,
>
> I checked out the CVS version and applied the patch, but I still have
> the problem.
>
> When I run it through gdb, I set breakpoints where ME_DUMMY is used
> (the function defined to check fs type) and it goes through all my
> mount points but the 'me->me_devname' variable never gets set to
> '/var/named/chroot/proc' and it never gets checked.
> It's as though this warning is not output by the program itself, but
> by something else when access to that mount point is attempted.
>
> So unless I've done something wrong I would say this patch doesn't fix
> my problem. If I get some more time I will debug it some more and see
> if I can find the point where the error occurs.
>
> n0dalus.
>

I managed to get the problem fixed by adding 'proc' to the list of
filesystems to mark as dummy. I'm not sure if this is the right thing
to do (do people want to be able to see proc mounts by default?), but
it works for me.

Attached is my updated version of the patch.

n0dalus.

coreutils-df-ignore-bind.patch
Description: Text Data