Gordon Messmer wrote:
Dave Burns wrote:

man page on find -prune was not clear to me, but I tried all combos I
can think of, nothing works as I'd wish:
...
[EMAIL PROTECTED] ~]$ sudo find /users/tburns -name .gvfs -prune
find: /users/tburns/.gvfs: Permission denied
[EMAIL PROTECTED] ~]$ sudo find /users/tburns -prune -name .gvfs
[EMAIL PROTECTED] ~]$ sudo find /users/tburns \( -prune -name .gvfs \)
[EMAIL PROTECTED] ~]$ sudo find /users/tburns \( -name .gvfs -prune \)
find: /users/tburns/.gvfs: Permission denied

You need to tell find what to do with files not named .gvfs:

find /users/tburns -name .gvfs -prune -o -print

Will not work.  As soon as the non-owner of .gvfs does a stat on the
directory, the error will be spit out.  find must "stat()" any item
it finds to handle the remainder of the predicate and POP goes the
error.

And now that I've logged out & back in and .gvfs is mounted again, I
can test the other suggested workaround involving remount. This also
does not work for me, though I may be giving the wrong form of mount
command:

[EMAIL PROTECTED] ~]$ sudo mount -o remount -o exec -o suid -o rw /users/tburns/.gvfs
[EMAIL PROTECTED] ~]$ sudo find /users/tburns/.gvfs
find: /users/tburns/.gvfs: Permission denied

I'm not sure what was mounted in the examples mentioned earlier. My understanding of FUSE is that the process providing the FS is the one that must perform the mount. Remounting manually should mount nothing.



--
----------------------------------------------------------------------
- Rick Stevens, Systems Engineer                      [EMAIL PROTECTED] -
- AIM/Skype: therps2        ICQ: 22643734            Yahoo: origrps2 -
-                                                                    -
-               500: Internal Fortune Cookie Error                   -
----------------------------------------------------------------------

--
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines

Reply via email to