Displaying 3 results from an estimated 3 matches for "cleanup_fnam".
Did you mean:
cleanup_fname
2006 May 18
1
Partial files left on SIGINT
Hi,
As the man page says, the --partial flag is to "keep partially
transferred files". I'm assuming if I don't have partial flag any
partially transferred files should be deleted. However this is not what
I'm seeing.
Example:
(Using a big file so that rsync times a while to run. This gives me time
to hit CTRL-C for the SIGINT).
> mkdir example
> dd if=/dev/zero
2004 May 29
1
[patch] Filename conversion
...leanup.c
--- rsync-2.6.2/cleanup.c 2004-01-27 10:14:33.000000000 +0200
+++ rsync-2.6.2-fnameconv.clean/cleanup.c 2004-05-29 21:17:08.000000000 +0300
@@ -119,6 +119,7 @@ void _exit_cleanup(int code, const char
finish_transfer(cleanup_new_fname, fname, cleanup_file);
}
io_flush(FULL_FLUSH);
+ cleanup_fname_convert();
if (cleanup_fname)
do_unlink(cleanup_fname);
if (code) {
diff -rupNP rsync-2.6.2/errcode.h rsync-2.6.2-fnameconv.clean/errcode.h
--- rsync-2.6.2/errcode.h 2003-12-15 10:04:14.000000000 +0200
+++ rsync-2.6.2-fnameconv.clean/errcode.h 2004-05-29 21:17:08.000000000 +0300
@@ -34,6 +3...
2004 May 10
2
read error produces null-byte-filled destination file
I've run into a bug in the IO handling when reading a file. Suppose I
have a file that lives on an NFS filesystem. That filesystem is NOT
being exported with auth=0 permissions. So, if I try to access a file
as root, it successfully opens the file, but subsequent reads fail with
EACCES. This produces a destination file full of null bytes. I
noticed this with 2.5.7, but checked 2.6.2 as