Package: rsync Version: 3.0.7-2 Severity: normal This is possibly related to #595967.
Last week I set off an rsync job of several terabytes of data and then rushed to catch a train. On return, I found the target empty, and yet the rsync was still running. The reason was insufficient permissions to write to the target. Meanwhile, rsync burned resources for nothing. If rsync fails to write a file, why continue to read and transfer the file? Shouldn't the protocol abort (and rsync exit with failure)? -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.36-trunk-amd64 (SMP w/8 CPU cores) Locale: LANG=en_NZ, LC_CTYPE=en_NZ.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages rsync depends on: ii base-files 5.9 Debian base system miscellaneous f ii libacl1 2.2.49-4 Access control list shared library ii libc6 2.11.2-7 Embedded GNU C Library: Shared lib ii libpopt0 1.16-1 lib for parsing cmdline parameters ii lsb-base 3.2-26 Linux Standard Base 3.2 init scrip rsync recommends no packages. Versions of packages rsync suggests: ii openssh-client 1:5.6p1-2 secure shell (SSH) client, for sec ii openssh-server 1:5.6p1-2 secure shell (SSH) server, for sec -- no debconf information -- .''`. martin f. krafft <[email protected]> Related projects: : :' : proud Debian developer http://debiansystem.info `. `'` http://people.debian.org/~madduck http://vcs-pkg.org `- Debian - when you have better things to do than fixing systems
digital_signature_gpg.asc
Description: Digital signature (see http://martin-krafft.net/gpg/)
