[BackupPC-users] rsync --exclude options - why are they stripped?

This question has been asked before (http://sourceforge.net/p/backuppc/mailman/message/22459100/, http://sourceforge.net/p/backuppc/mailman/message/31066154/), but I haven't seen any answers, so I ask again, because this is something I really want to understand. The Documentation of RsyncArgsE

[BackupPC-users] rsync --exclude options - why are they stripped?

Got it, finallly - the include/exclude options are sent to the client via the rsync protocol. From the XferLog: Sent exclude: /trash Sent exclude: /tmp Sent exclude: *.iso Sent exclude: *.rpm This happens to both the RsyncExtraArgs and backupExclude / BackupInclude options. So it's all fine.

[BackupPC-users] rsync --exclude options - why are they stripped?

... this works for both the rsync and rsyncd protocols. +-- |This was sent by martin.wi...@ts.fujitsu.com via Backup Central. |Forward SPAM to ab...@backupcentral.com. +-

[BackupPC-users] rsync --exclude options - why are they stripped?

Holger Parplies wrote: > > I'd have to look at the current code closely to be sure, but from memory, > rsync sends the in-/excludes via the rsync protocol exchange rather than on > the command line. Your XferLOG should contain lines starting with > "Sent exclude" (or include, I suppose). I remem

Re: [BackupPC-users] rsync --exclude options - why are they stripped?

Hi, mwilck wrote on 2014-11-12 05:29:23 -0800 [[BackupPC-users] rsync --exclude options - why are they stripped?]: > [...] > The Documentation of RsyncArgsExtra [...] mentions explicity its usefulness > for defining rsync-style include/exclude rules [...]. The code explicity > r