It's almost a year later, but since Google quickly led me to this post in the
archives, I guess the answer may be useful to others.
Had the same error today, in the same situation: cwrsync in Win7x64, batch file
started by Local computer Policy on shutdown.
There is something special in the
Thanks Joe for the reply:
1) why do you say to use fuzzy twice? Do you mean in both directions?
2) I have to mention that the remote system is a Synology NAS, which for
whatever reason (I can't think about), doesn't support symlinks, even in
the same disk volume or share!
But I could make some
OK , but then the solution with symlinks is equivalent, just with the right
options for rsync.
Make the link.
Sync + exclude.
Remove the link.
Don't have to live with the folder on the source.
*___Gionata Boccalini*
2015-06-08 22:49 GMT+02:00 Michael Johnson - MJ m...@revmj.com:
I should describe the problem more in details, but I believe this is off
topic for this list.
The FolderA is named Musica (in Italian) because.. I like it that way..
and is in my home folder.
PC # /home/gionata/Musica
FolderB MUST be named music, in my home folder on the NFS filesystem,
NAS #
The symlinks was mostly a shot in the dark. They're often useful when
you need synonyms.
The --fuzzy: I believe once handles different names and the second one
adds different locations.
I have thought about using it for issues I have reorganizing collections
of media files, but never got
