Bug#318609: rsync should do more checks before sending

2008-03-03 Thread Paul Slootman
close 318609 3.0.0-1
thanks

On Sat 16 Jul 2005, Marc Lehmann wrote:
 
 I just made an 16 hour upload using rsync:
 
rsync -avzP some_big_avi.avi ruth:var/www/prop*/.
 
 But I mistypes and forgot the / at the start of the path, so rsync
 (correctly) tried to use a root-relative path.
 
 After 16 hours of upload, I got his message:
 
rsync: mkstemp /root/var/www/prop*/...GVL2ea failed: No such file or 
 directory (2)
sent 714439115 bytes  received 42 bytes  44478.70 bytes/sec
total size is 736929792  speedup is 1.03
rsync error: some files could not be transferred (code 23) at main.c(789)

This is now better in the current 3.0.0-1 version:

$ rsync -avzP some_big_avi.avi olijfje:tmp/anzzz*/.
building file list ... 
1 file to consider
rsync: push_dir#3 /home/paul/tmp/anzzz* failed: No such file or directory 
(2)
rsync error: errors selecting input/output files, dirs (code 3) at main.c(632) 
[receiver=3.0.0pre7]
rsync: connection unexpectedly closed (8 bytes received so far) [sender]
rsync error: error in rsync protocol data stream (code 12) at io.c(600) 
[sender=3.0.0pre10]

This happened immediately, no data transferred yet.
Hence I'm now closing this report.

Note that -z isn't so useful with .avi ...


Paul Slootman



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#318609: rsync should do more checks before sending

2005-07-16 Thread Marc Lehmann
Package: rsync
Version: 2.6.4-4
Severity: wishlist

I just made an 16 hour upload using rsync:

   rsync -avzP some_big_avi.avi ruth:var/www/prop*/.

But I mistypes and forgot the / at the start of the path, so rsync
(correctly) tried to use a root-relative path.

After 16 hours of upload, I got his message:

   rsync: mkstemp /root/var/www/prop*/...GVL2ea failed: No such file or 
directory (2)
   sent 714439115 bytes  received 42 bytes  44478.70 bytes/sec
   total size is 736929792  speedup is 1.03
   rsync error: some files could not be transferred (code 23) at main.c(789)

First of all, there is no message that that file could not be
tranSecondly, the message it outputs is not very helpful in finding out
what is wrong, as a file named ...GVL2ea was never specified. (although
it's obvious as it's the only one for this invocation).

And lastly, of course, the problem was there from the very beginning, so
rsync shouldn't wait till it has transferred the whole file just to find
out that it had to throw it away :)




-- System Information:
Debian Release: testing/unstable
  APT prefers testing
  APT policy: (700, 'testing'), (500, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/dash
Kernel: Linux 2.6.12.1
Locale: LANG=C, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)

Versions of packages rsync depends on:
hi  libc6   2.3.2.ds1-21 GNU C Library: Shared libraries an
ii  libpopt01.7-5lib for parsing cmdline parameters

-- no debconf information


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]