Gordon Messmer wrote:
Rick Stevens wrote:
Gordon Messmer wrote:
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
Rick Stevens wrote:
Gordon Messmer wrote:
If -name is the first predicate, and you prune matches, find will not
need to stat() the directory entry:
Sorry, won't work for GVFS filesystem mountpoints. As soon as the
non-owner touches the inode, the error occurs.
...
Note that test was on
Gordon Messmer wrote:
Rick Stevens wrote:
Gordon Messmer wrote:
If -name is the first predicate, and you prune matches, find will not
need to stat() the directory entry:
Sorry, won't work for GVFS filesystem mountpoints. As soon as the
non-owner touches the inode, the error occurs.
...
Rick Stevens wrote:
Nice to hear...or is it a change in GVFS?
No, FUSE hasn't changed. The GVFS filesystem remains private to the
user who mounted it.
--
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines:
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
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
Rick Stevens wrote:
Gordon Messmer wrote:
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
On Sat, Nov 1, 2008 at 6:00 PM, Joe Smith [EMAIL PROTECTED] wrote:
Can you just skip the .gvfs items specifically, by name, with -prune?
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
Dave Burns wrote:
On Sat, Nov 1, 2008 at 6:00 PM, Joe Smith [EMAIL PROTECTED] wrote:
Can you just skip the .gvfs items specifically, by name, with -prune?
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
Joe Smith wrote:
Dave Burns wrote:
...
Not sure if it is a bug in find or gvfs, but -xdev and -mount do not
help with this problem.
I've never seen these options work, ever. I sure would like to know why,
or what I'm doing wrong, it would be handy to be able to use them.
That depends on
Gordon Messmer wrote:
... If you've ever seen find return results from a
directory that it wasn't told to search when using -xdev or -mount, then
that would be a bug. I've never seen find misbehave in that way, though.
Well, there you go: it works as expected now.
I should know better;
Dave Burns wrote:
...
Not sure if it is a bug in find or gvfs, but -xdev and -mount do not
help with this problem.
I've never seen these options work, ever. I sure would like to know why,
or what I'm doing wrong, it would be handy to be able to use them.
Can you just skip the .gvfs items
On Wed, Oct 29, 2008 at 5:17 PM, R. G. Newbury [EMAIL PROTECTED] wrote:
This problem got me a while ago, and discussed here.
http://www.mail-archive.com/fedora-list@redhat.com/msg18051.html is
all I found, no help there.
The problem is the mount
On Thu, 30 Oct 2008 08:34:01 -1000
Dave Burns [EMAIL PROTECTED] wrote:
I think I will probably just make a kludgey workaround - pipe error
messages to /dev/null - always fun.
My brother just sent me this email:
QUOTE:
My problem (OK - maybe just one of my problems) is that I can't
figure out
On Thu, Oct 30, 2008 at 8:47 AM, Frank Cox [EMAIL PROTECTED] wrote:
Does anyone know how this works and what the real solution is? (Is there a
real solution?)
Yeah, is there any gnome setting that lets you turn gvfs off or make
it act reasonable?
Dave
--
fedora-list mailing list
On Thu, Oct 30, 2008 at 8:49 AM, Dave Burns [EMAIL PROTECTED] wrote:
On Thu, Oct 30, 2008 at 8:47 AM, Frank Cox [EMAIL PROTECTED] wrote:
Does anyone know how this works and what the real solution is? (Is there a
real solution?)
Yeah, is there any gnome setting that lets you turn gvfs off or
Frank Cox wrote:
On Thu, 30 Oct 2008 08:34:01 -1000
Dave Burns [EMAIL PROTECTED] wrote:
I think I will probably just make a kludgey workaround - pipe error
messages to /dev/null - always fun.
My brother just sent me this email:
QUOTE:
My problem (OK - maybe just one of my problems) is that
Patrick O'Callaghan wrote:
On Wed, 2008-10-29 at 12:27 -1000, Dave Burns wrote:
[...]
.gvfs is using some secret sauce that I don't understand to prevent
root from accessing it. Is there some ACL stuff going on here?
(getfacl results are boring.) File locking? (lsof says it is not
open.)
On Thu, Oct 30, 2008 at 9:33 AM, Les Mikesell [EMAIL PROTECTED] wrote:
I usually throw in the -mount option to find on general principles to keep
it from walking into isos or nfs mounts that might be in arbitrary places
and explicitly list the mount points I want if it has to span them.
Not
On Thu, 2008-10-30 at 09:43 -1000, Dave Burns wrote:
On Thu, Oct 30, 2008 at 9:33 AM, Les Mikesell [EMAIL PROTECTED] wrote:
I usually throw in the -mount option to find on general principles to keep
it from walking into isos or nfs mounts that might be in arbitrary places
and explicitly
I have a cron job that runs 'find /' as root, keeps blowing up when
encountering ~/.gvfs in my home dir. Permissions are set like so:
ls -la ~/.gvfs
total 4
dr-x-- 2 tburns isys0 2008-10-13 07:43 .
drwxr-xr-x 73 tburns root 4096 2008-10-24 11:49 ..
As owner of dir, no problem:
find
On Wed, 2008-10-29 at 12:27 -1000, Dave Burns wrote:
[...]
.gvfs is using some secret sauce that I don't understand to prevent
root from accessing it. Is there some ACL stuff going on here?
(getfacl results are boring.) File locking? (lsof says it is not
open.) Corruption? How can it be that
Dave Burns wrote:
I have a cron job that runs 'find /' as root, keeps blowing up when
encountering ~/.gvfs in my home dir. Permissions are set like so:
ls -la ~/.gvfs
total 4
dr-x-- 2 tburns isys0 2008-10-13 07:43 .
drwxr-xr-x 73 tburns root 4096 2008-10-24 11:49 ..
As owner of dir,
No Joy.
On Wed, Oct 29, 2008 at 1:04 PM, Patrick O'Callaghan
[EMAIL PROTECTED] wrote:
You might try the -mount (or -xdev) options to 'find', but that will
also restrict you from crossing into other mounted filesystems.
sudo find /users/tburns/ -xdev|grep gvfs
find: /users/tburns/.gvfs:
Patrick O'Callaghan wrote, On 10/29/2008 07:04 PM:
(Does anyone else think .gvfs is a PITA?)
+1
And wondering how much grief it is going to cause me while administrating an
NFS|AFS|SMB server for home directories that I need to back up.
I suppose I have a little while before RHEL gets
On Wed, Oct 29, 2008 at 1:16 PM, Rick Stevens [EMAIL PROTECTED] wrote:
Dave Burns wrote:
at least give me a hint what to do or what to google for.
.gvfs is a virtual filesystem and doesn't follow normal filesystem
semantics (witness the fact the size of it is zero).
So... It is not a
On Wed, 29 Oct 2008 12:27:32 -1000
Dave Burns [EMAIL PROTECTED] wrote:
I have a cron job that runs 'find /' as root, keeps blowing up when
encountering ~/.gvfs in my home dir. Permissions are set like so:
My brother ran into this issue just the other day. I just asked him for his
input and he
On Wed, Oct 29, 2008 at 1:34 PM, Frank Cox [EMAIL PROTECTED] wrote:
On Wed, 29 Oct 2008 12:27:32 -1000
check whether .gvfs is a mounted
filesystem (it probably is).
Yep.
Why can root not access it?
Perhaps because there is no read permission in the mount point?
I created an identical
On Wed, 29 Oct 2008 13:43:09 -1000
Dave Burns [EMAIL PROTECTED] wrote:
So... bro has no suggestion for a workaround?
From the message he sent me the other day when he resolved the issue on his
computer:
QUOTE:
turns out that it was mounted under something...when I unmounted
directory, I could
Dave Burns wrote:
On Wed, Oct 29, 2008 at 1:34 PM, Frank Cox [EMAIL PROTECTED] wrote:
On Wed, 29 Oct 2008 12:27:32 -1000
check whether .gvfs is a mounted
filesystem (it probably is).
Yep.
Why can root not access it?
Perhaps because there is no read permission in the mount point?
I created
Message: 4
Date: Wed, 29 Oct 2008 19:10:28 -0400
From: Todd Denniston [EMAIL PROTECTED]
Subject: Re: OT: find command permissions: how to exclude dir?
To: Community assistance, encouragement, and advice for using
Fedora. fedora-list@redhat.com
Message-ID
On Wed, 2008-10-29 at 23:17 -0400, R. G. Newbury wrote:
Message: 4
Date: Wed, 29 Oct 2008 19:10:28 -0400
From: Todd Denniston [EMAIL PROTECTED]
Subject: Re: OT: find command permissions: how to exclude dir?
To: Community assistance, encouragement
32 matches
Mail list logo
