On Fri 29 Apr 2005, Jaume Guasch wrote:
>
> With (old) rsync 2.6.3-2 I used the following options to syncronize
> different computers:
>
> DATA=`date '+%Y-%m-%d'`
> RSYNCGET="rsync -abxHzu --progress -v --suffix=.~${DATA} --exclude="*.a"
> --exclude="*.o" --exclude="*~*" --exclude="*.exe" --exclude=".nfs*"
> --exclude="msg.*" --exclude="lock" --exclude="*\#" --exclude=".\#*"
> --exclude="Backup" --exclude="pine-bin.linux" --delete --delete-after -e
> ssh "
Is this the exact line from the script? This looks suspicious, as the
command is enclosed in double quotes, but the command also uses
unescaped double quotes which hence will not be put into the variable
$RSYNCGET.
> ${RSYNCGET} server:dir dir
This becomes:
rsync -abxHzu --progress -v --suffix=.~2005-05-02 --exclude=*.a --exclude=*.o
--exclude=*~* --exclude=*.exe --exclude=.nfs* --exclude=msg.* --exclude=lock
--exclude=*# --exclude=.#* --exclude=Backup --exclude=pine-bin.linux --delete
--delete-after -e ssh server:dir dir
You're probably lucky that because of the --suffix= prefix, the * won't
be expanded (as it doesn't match anything).
Note also that "-e ssh" is redundant.
> This makes a full copy, and leaves a backup copy of every changed and
> deleted file in the client, with a name which contains the date
> of the transfer.
>
> Since I installed 2.6.4, the same command does not perform the
> same:
>
> If a file is deleted in the server, it will be deleted in the client,
> WITHOUT leaving a backup copy.
>
> Expected behaviour: a backup copy should be left in the client
I've confirmed this, and have filed a bug against the upstream source.
Upstream is usually very quick with fixes for these matters. I'll upload
a fixed version as soon as the fix is available.
Paul Slootman
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
