[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [rdiff-backup-users] Descending into excluded directories?
From: |
Bret Martin |
Subject: |
Re: [rdiff-backup-users] Descending into excluded directories? |
Date: |
Wed, 06 Sep 2006 15:00:11 -0400 |
On Wed, 06 Sep 2006 14:36:26 EDT Bret Martin wrote:
[...]
> Naturally, I would not like rdiff-backup to back up these remote
> filesystems. I have this line in my exclusion list:
>
> /home/*/.sshfs/
>
> However, rdiff-backup descends into /home/bam/.sshfs/ anyway.
[...]
My exclusion pattern seems to be the problem. I was using a trailing
'/' as rsync(1) does -- under rsync that makes the pattern match a
directory and nothing else. (For me, at least, it also makes the
exclude list a lot clearer -- I can tell what is a directory and what is
a file.)
If I change the line above to
/home/*/.sshfs
then it works as expected.
For some reason I don't understand, though, I have a number of other
exclude patterns that end with '/' that have always worked correctly.
Does anyone understand why this would be?
The only way I can think of in which /home/bam/.sshfs/ is special
is that it's an afuse filesystem:
afuse on /home/bam/.sshfs type fuse (rw,nosuid,nodev,allow_other,user=bam)
and the other /-terminated excluded directories I had are often
subdirectories of some other filesystem:
/amd/
/fs/
/home/*/.galeon/mozilla/galeon/Cache/
/home/*/.mozilla/**/Cache/
/home/*/.netscape/cache/
but not always:
/net/
/proc/
/scratch/
yet those have always been excluded when specified with the trailing /...
--Bret