mkstemp fails but data still transferred
sharris at myra.com
Wed Mar 23 17:52:34 GMT 2005
I see and it makes sense to optimise the file transfer process, but in
carrying on with a transfer when the temporary file cannot be created can
(in our case) result in quite a large amount of data being transferred
over the network (we have more than a few files in the 6-8GB range) which
is not optimal.
As a work around we are probably going to change the way our scripts work that
wrap around rsync.
Thanks for the help.
Cheers - Steve
> The Documentation section of the rsync web site has a "How Rsync Works" page:
> originally written by the late JW Schultz.
> In the pipeline section you'll see that communication is unidirectional.
> One of rsync's many advantages is streaming unidirectional pipelines.
> Not having two-way chatter helps speed up file transfers.
> Since it is optimized for the normal case where there are no problems
> on the receiving end, the receiver has no way to tell the sender to
> stop sending file content when there is a problem, and must accept and
> discard the remainder of the file (which is what you are seeing).
> Subsequent file transfers might be successful, so it can't abort, yet.
> Hope that helps.
> John Van Essen Univ of Minn. Alumnus <vanes002 at umn.edu>
> To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync
> Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
More information about the rsync