search for: safe_fname

...ime = now_time-delete_mdays*24*60*60; - time_t file_modtime = local_file_list->files[i]->modtime; - - if (delete_mdays!=-1 && file_modtime>mday_time){ - if(verbose) - rprintf(FINFO, - "not deleting %s, age %d days, need %d days\n", - safe_fname(f), - (int)(now_time-file_modtime)/24/60/60, - delete_mdays); - continue; - } - - if (make_backups && (backup_dir || !is_backup_file(f))) { make_backup(f); if (verbose) { rprintf(FINFO, "deleting %s\n", safe_fname(f));...

Has anyone ever seen this happen when using rsync ? I'm trying to send a series of =~ 300k files down the line, but for some reason, rsync thinks each file is 17592186044416 bytes long! The same behaviour occurs when using rsync to copy files locally. Partial output follows...any help appreciated! Cheers, P [root@grappa llog]# ls -al /IFX/llog/logs.109051.gz -rw-rw---- 1 informix

...update existing files */ if (verbose > 1) { - rprintf(FINFO, "not creating new file \"%s\"\n", + rprintf(FINFO, "not creating new %s \"%s\"\n", + S_ISDIR(file->mode) ? "directory" : "file", safe_fname(fname)); } return;

...} --- 204,214 ---- } if (!kept && S_ISDIR(file->mode)) { ! if (robust_move(fname, buf) != 0) { ! rsyserr(FERROR, errno, "keep_backup failed: % s -> \"%s\"", ! full_fname(fname), safe_fname(buf)); } kept = 1; }

Hi again. I just spotted another peculiarity when inspecting the rsync log. When using --compare-dest, source files that have permissions that differ from the "comparables" are not logged, unless you're using -i. Here's a testing session: $ ls -lR .: total 12 drwxr-xr-x 2 vidar users 4096 2005-03-31 14:16 cmp/ drwxr-xr-x 2 vidar users 4096 2005-03-31 14:23 dst/

There's a bug reported in Debian about the tty being screwed up by wierd filenames, see http://bugs.debian.org/bug=242300 On the one hand, find will also do this. On the other hand, ls will replace such chars with a question mark. Upon inspection, it appears to be fairly simple to also do this in rsync (in the rwrite() function). Here's a patch. Opinions? Perhaps don't do it

There's a rather old bug report in Debian's bug tracking system (see http://bugs.debian.org/27126) about wanting to be able to specify the maximum file size, as well as the minimum file size. Here's the text: Sometimes, it's useful to specify a file size range one is interested in. For example, I'd like to keep an up-to-date mirror of Debian, but I currently

...(i == -1) { if (phase == 0) { + write_batch_monitor_out = old_monitor; phase++; csum_length = SUM_LENGTH; write_int(f_out, -1); @@ -173,7 +187,7 @@ if (dry_run) { if (!am_server && verbose) /* log the transfer */ rprintf(FINFO, "%s\n", safe_fname(fname2)); - write_int(f_out, i); + write_int(f_alt, i); continue; } @@ -224,8 +238,8 @@ safe_fname(fname), (double)st.st_size); } - write_int(f_out, i); - write_sum_head(f_out, s); + write_int(f_alt, i); + write_sum_head(f_alt, s); if (verbose > 2) { rprintf(F...

Attached is a patch that makes window strides constant when files are walked with a constant block size. In these cases, it completely avoids all memmoves. In my simple local test of rsyncing 57MB of 10 local files, memmoved bytes went from 18MB to zero. I haven't tested this for a big variety of file cases. I think that this will always reduce the memmoves involved with walking a large

...7 +256,7 @@ if (server_filter_list.head && check_filter(&server_filter_list, fname, - S_ISDIR(file->mode)) < 0) { + S_ISDIR(file->mode)) == M_EXCLUDE) { if (verbose) { rprintf(FINFO, "skipping server-excluded file \"%s\"\n", safe_fname(fname)); diff -ur ../rsync-HEAD-20050125-1221GMT.orig/options.c ./options.c --- ../rsync-HEAD-20050125-1221GMT.orig/options.c Tue Jan 25 12:21:14 2005 +++ ./options.c Mon Jan 31 14:28:25 2005 @@ -307,6 +307,8 @@ rprintf(F," --exclude-from=FILE exclude patterns listed in FILE\n"...