On 5 March 2010 13:36, Paul Slootman <[email protected]> wrote: > On Fri 05 Mar 2010, Frederik Braun wrote: > >> I just tried again, it appears that my exclude-statement appears to be >> incorrect - it still looks at .gvfs. >> These are my entries: >> /home/chosenone/.gvfs >> /home/chosenone/.gvfs* > > Excludes must be relative to the root of the transfer. > Hence if the path is /home, the excludes must be: > /chosenone/.gvfs* >
I had this same problem a while back: I've been trawling about trying to find where I carefully wrote down the solution, but it appears I didn't... I think, though, that it was because of an ubuntu bug in the ownership of .gvfs - root couldn't even see the existence of the directory. I had to umount the directory on the client machine causing the problem, as that user. Then, because the gvfs remounts at boot, I stuck this in as a cron job to run before the dirvish backup: ##the dirvish backup from xios keeps failing because of a bug where the .gvfs file in /home/laurie has bad permissions. ##This fixes the bug, but it reappears on machine reboot so will set it as cron job to run just before backup umount /home/laurie/.gvfs aptitude reinstall gvfs gvfs-backends gvfs-bin gvfs-fuse libgvfscommon0 I don't even know if I still need that running, bug might be fixed now - forgot all about it to be honest. Jenny _______________________________________________ Dirvish mailing list [email protected] http://www.dirvish.org/mailman/listinfo/dirvish
