Evren writes:
> Is this a bug or what? Because of this, also the examples in the configuration
> file where --exclude are do not function at all. Is there a reason to strip
> the
> --exclude arguments at all?
The include/exclude arguments are sent to the remote child via the
socket connection, not via the command-line arguments.
The exclude/include arguments are still in the $rsyncArgs variable,
which is passed to File::RsyncP->new(). That code then extracts
and remembers the exclude/include arguments with this code:
#
# First extract all the exclude related options for processing later
#
return if ( !$p->getoptions(
"exclude=s", sub { optExclude($rs, @_); },
"exclude-from=s", sub { optExclude($rs, @_); },
"include=s", sub { optExclude($rs, @_); },
"include-from=s", sub { optExclude($rs, @_); },
"cvs-exclude|C=s", sub { optExclude($rs, @_); },
) );
Craig
------------------------------------------------------------------------------
Crystal Reports - New Free Runtime and 30 Day Trial
Check out the new simplified licensing option that enables
unlimited royalty-free distribution of the report engine
for externally facing server and web deployment.
http://p.sf.net/sfu/businessobjects
_______________________________________________
BackupPC-devel mailing list
BackupPC-devel@lists.sourceforge.net
List: https://lists.sourceforge.net/lists/listinfo/backuppc-devel
Wiki: http://backuppc.wiki.sourceforge.net
Project: http://backuppc.sourceforge.net/
