On Sun, Apr 22, 2012 at 08:32:25AM -0400, gene heskett wrote: > If I have in my excludes file: > > ./gene/.gvfs > > Then there is no complaint about the lack of access perms in the emailed > report. > > However, from what I understand about the anchoring process, that line > should also cause /home/gene to be bypassed, and that effectively shuts > down the reason to do the backup in the first place.
Its is probably quiet because there is no such entity "./gene/.gvfs". I imagine your starting directory for that DLE is /home/gene. In that case your above syntax would refer to /home/gene/gene/.gvfs. > > Having the line: > ./.gvfs > in the exclude file doesn't shut up the incessant mewling about it from > amanda because due to the way the perms are set on that subdir, not even > root can access it. So I haven't a clue why its there, or what in tuncket > its doing. It has something to do with Ubuntu's use of the Global Virtual > File System. I think. > > Ideas? Clarifications? > I remember the same lack of access to .gvfs on my Ubuntu system (no longer have it). My two Fedora systems allow normal (i.e. expected) access to .gvfs. Gnome's use of ~/.gvfs as the mount point for various things seems similar to the pseudo directory specified for the auto-filesystem-mounter if it is used. I recall funny accessibility to those directories. Auto-mount points and .gvfs share another trait. Unlike ordinary directories, things get mounted "in them" rather than "on them". I.e., when something is mounted on .gvfs, another it is like a virtual subdirectory of .gvfs is created and that is the actual mount point. This technique allows multiple things to be mounted there. I find it interesting that .gvfs has size "0", even when something is mounted in there. No ideas on how to deal with the error messages. jl -- Jon H. LaBadie [email protected] 11226 South Shore Rd. (703) 787-0688 (H) Reston, VA 20190 (609) 477-8330 (C)
