The problem right now is that nobody is putting this issue completely at rest. Oh, good idea... Results 1 to 10 of 10 Thread: Bash: Avoiding .gvfs error from tar Thread Tools Show Printable Version Subscribe to this Thread… Display Linear Mode Switch to Hybrid Mode Switch to But since I use encfs (that uses fuse) I can tell you that root wont access the files, unless you mount the colume with --public, and you can only do that this contact form
Mountain Linux - Software 5 04-03-2008 01:50 PM All times are GMT -5. Bicycling is the perfect union of driver and engine. Nikolaus Rath (nikratio) wrote on 2008-11-17: #48 Phillip Susi
I've got a funny problem: I have some files lying around in /root/bla/, all these files are 644 and /root/bla/ is 755. on 2008-05-01 336 This bug affects 54 people Affects Status Importance Assigned to Milestone gvfs Edit Confirmed Medium gnome-bugs #560658 You need to log in to change this bug's status. This is for security reasons, because you don't always have control over user rigths on remote systems. Meaning?
At the end of the day programs simply have to deal with access denied errors, even when run as root. Barratt"
Why won't curl download this link when a browser will? Originally Posted by Penguin Guy However I would advise changing some other things: Add -p to retain file permissions Oh, good idea... Shirish Agarwal (shirishag75) wrote on 2008-10-23: Re: Superuser cannot access ~/.gvfs folder when mounted #26 Hi all, This is a Hardy updated/upgraded machine. https://bugs.launchpad.net/bugs/225361 I thought that maybe the file was held open by a process and that might have been the reason why root was unable to move the file, but that doesn't appear
That is not spamming. In case I want to "sudo lso | grep ...". –user276851 Sep 24 '15 at 18:36 add a comment| Your Answer draft saved draft discarded Sign up or log in Changed in gvfs (Ubuntu): status: Triaged → Fix Released Ralph Corderoy (ralph-inputplus) wrote on 2013-03-06: #72 So can rsync --one-file-system, find, etc., now stat the inode to know it's another filesystem How do I handle this?
Sahasrabuddhe (sameerds) wrote on 2008-11-18: Re: ~/.gvfs causes various errors #52 Philip Susi wrote: > Maybe 20 years ago, but these days being root does NOT mean you can do > Sebastien Bacher (seb128) wrote on 2008-06-16: #21 that's no issue but 8 comments have been added in a few days now which means 8 mails sent to whoever is subscribed to Thank you for reporting the bug, which will now be closed. Also, it creates the archive regardless.
Phillip Susi (psusi) wrote on 2008-11-18: #54 If rsync errors out immediately because it gets an access denied error opening one source file, then yes, I'd say you should file a weblink Nikolaus Rath (nikratio) wrote on 2009-04-25: #59 No, that's not true. Workarounds =========== * bind-mount the file system you want to backup beforehand (see comment #67) See also ======= * Excellent description of the problem in bug 227724 * fuse-devel mailing list Well, too bad.
How safe is 48V DC? gvfs lsof share|improve this question edited Jul 9 '12 at 13:10 hexafraction 13.4k94881 asked Jan 24 '11 at 16:50 NES 10.4k3069109 What @jmtd said is correct. So it looks like there IS a bug somewhere, and it would be nice to see it fixed. navigate here pt123 (pt123) wrote on 2008-06-14: #16 Me too same problem as Ralph sudo strace -e trace=lstat64 stat /home/pt123/.gvfs/ [sudo] password for pt123: lstat64("/home/pt123/.gvfs/", 0xbffba7b4) = -1 EACCES (Permission denied) stat: cannot
In the fstab for 12 it says to add after defaults ,usrjquota=aquota.user,grpjquota=aquota.group,jqfmt=vfsv0 and in 11 it says to add ,usrquota,grpquota Let me add that my system is not 64bit and here By definition, there are already enough people to do that.« -J.H. I'm finding it's cropping up more and more in my daily activities, and I want to get rid of it.
Fuse 2.8.4 has now been uploaded to unstable, it should be on your mirror in a few hours. This information was last pulled 15 hours ago. Having a problem logging in? root) cannot access a fuse filesystem, and not even stat the mountpoint: $ sudo stat .gvfs stat: cannot stat `.gvfs': Permission denied $ sudo ls -la ls: cannot access .gvfs: Permission
The problem is that people are having utilities fail when they run into .gvfs because root can't access it ( and this is by design, not a bug ). Ah, yes you're right; in that case - remember to use -p if and when you extract it. The manpage from our repos seemed to have been lying; see this thread. http://culturahq.com/cannot-stat/cannot-stat-ath-pci-ko.html Thanks for this.