rename(2) errno processing

Hello, I've been porting rsync-3.0.7 to run on UWIN, an ATT Labs open source project, supporting a Unix environment on Windows. The code configured easily and compiled without any modifications or ifdef's added to the code. The backup test was failing because it didn't create a subdirectory.

Re: Rsync command failing as a Cron Tab

Thanks! This seems to have been the problem. After finding the information cron was spitting out to the unix mail, it was apparent that the splats (*) used to short cut the paths so the command would fit into the max length of the command line where giving problems when run by cron. Don't

ENOTDIR for nonexistent path components

On Thu, 2010-09-23 at 09:20 -0400, Jeff Fellin wrote: I've been porting rsync-3.0.7 to run on UWIN, an ATT Labs open source project, supporting a Unix environment on Windows. The code configured easily and compiled without any modifications or ifdef's added to the code. The backup test was

recent discussion regarding 'checksums'

Hi. Wanted to add something. There was recent talk about the use of 'checksums' by rsync to determine how or what parts of a file to copy. Something like that. Anyways, it just so happens that I have a number of files here that rsync completely fails to update... l -isT */* ; md5 -r */* ; sha1