On Wed, 2009-03-11 at 16:13 +1100, Cameron Simpson wrote:
> I know this may seem nonsensical, but I wanted to issue an rsync
> invocation that synced nothing at all. (I wanted to avoid a sync by
> fiddling a config file in some automation rather than changing to
> auomation to have a skip-the-rsync
I know this may seem nonsensical, but I wanted to issue an rsync
invocation that synced nothing at all. (I wanted to avoid a sync by
fiddling a config file in some automation rather than changing to
auomation to have a skip-the-rsync mode.)
Anyway, it seems to me with rsync-3.0.5 that one of:
-
Typically rsync exits and reports an error such as:
rsync: writefd_unbuffered failed to write 4 bytes [sender]: Broken
pipe (32)
rsync: write failed on "/Volumes/Backup/big_file.dmg": No space left
on device (28)
rsync: connection unexpectedly closed (67174 bytes received so far)
[sender]
r
Some of my users have reported problems with rsync puking on locked
folders. The errors typically look like this:
rsync -aNHAXx --fileflags --force-change --no-inc-recursive / /Volumes/
Backup
rsync: mkstemp "/Volumes/SCSI Backup/Users/Ken/Library/Caches/
Metadata/Safari/Bookmarks/..DS_Sto
