Bug 8309 - Protect filter has no affect when in filter file.
Summary: Protect filter has no affect when in filter file.
Status: RESOLVED WORKSFORME
Alias: None
Product: rsync
Classification: Unclassified
Component: core (show other bugs)
Version: 2.6.9
Hardware: All All
: P5 normal (vote)
Target Milestone: ---
Assignee: Wayne Davison
QA Contact: Rsync QA Contact
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-07-19 05:39 UTC by Dan
Modified: 2011-08-01 06:02 UTC (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Dan 2011-07-19 05:39:49 UTC

    
Comment 1 Dan 2011-07-19 05:41:32 UTC
Sorry about that, I accidentally pressed enter when creating the issue.

When I specify a "protect" rule on the command line, all works smoothly. I.e.

    rsync --filter "P myfile.db" -POuhimrtyz --delete -n . user@host:~

But when I specify it in a file (e.g. .rsync-filter):

P myfile.db

    rsync -F -POuhimrtyz --delete -n . user@host:~

No success.

Thanks!
Comment 2 Wayne Davison 2011-08-01 06:02:31 UTC
The filter file needs to be on the destination server in order to affect an incremental delete.  If the destination may not have its filter files up-to-date (and you don't want to do a transfer of just the filter files first, before the main content), then use --delete-after.