[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [rdiff-backup-users] [bug] Excluding hidden files the wrong way does

From: Adrian Klaver
Subject: Re: [rdiff-backup-users] [bug] Excluding hidden files the wrong way doesn't result in an error
Date: Thu, 5 Jan 2017 06:44:39 -0800
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.6.0

On 01/04/2017 02:40 PM, Ilario wrote:
> 2017-01-04 20:11 GMT+01:00 Adrian Klaver <address@hidden>:
>> On 01/04/2017 11:00 AM, Ilario wrote:
>>> Excluding a hidden file without full path doesn't rise an error (as
>>> happens with non hidden files) and copies it anyway; e.g.
>>> mkdir temp
>>> cd temp
>>> mkdir .one
>>> mkdir .two
>>> mkdir three
>>> mkdir four
>>> rdiff-backup --exclude .one --exclude ./.two --exclude ./three . ../backup
>>> ls -a ../backup
>>> .  ..  four  .one  rdiff-backup-data
>>> copies also the .one file and gives no warning.
>> I am not seeing a .one file I see a .one/ directory
> Yes, sorry, I meant directory, anyway I can see the same behaviour with files.
>> so I would say you need
>> to do:
>> --exclude .one**
> Does this work for you? It doesn't for me...

I was going from memory and did not actually try the pattern. 
My memory was faulty:( 

Turns out I had the ** in the wrong place:

address@hidden:~/temp> rdiff-backup --exclude **one --exclude ./.two --exclude 
./three . ../backup

address@hidden:~/temp> ls -a ../backup/
.  ..  four  rdiff-backup-data

Adrian Klaver

reply via email to

[Prev in Thread] Current Thread [Next in Thread]