Displaying 9 results from an estimated 9 matches for "unchanged_fil".
Did you mean:
unchanged_file
2019 Mar 07
1
[PATCH] Bug fix for file comparison
Hi,
below you find a patch fixing a bug in the file comparison code: The
current code skips the unchanged_file() check when that check succeeded for
an earlier candidate, which could lead to accepting a file with a different
checksum as unchanged, for example.
Please be aware that the patch is untested.
Florian
diff --git a/generator.c b/generator.c
index a112da6..2df1b28 100644
--- a/generator.c
+++ b/...
2008 Jul 29
7
DO NOT REPLY [Bug 5644] New: Option to recheck basis dirs for existing dest files
https://bugzilla.samba.org/show_bug.cgi?id=5644
Summary: Option to recheck basis dirs for existing dest files
Product: rsync
Version: 3.1.0
Platform: All
OS/Version: All
Status: NEW
Severity: enhancement
Priority: P3
Component: core
AssignedTo: wayned@samba.org
ReportedBy:
2015 Sep 14
3
[Bug 11521] New: rsync does not use high-resolution timestamps to determine file differences
...le | grep Mod
If the diff shows a difference, then the rsync didn't copy afile's contents
over. However, note the stat info from the last two lines - the updated modify
timestamp *will* be synced, making an inconsistent sync.
The following patch adds a check of the high-res timestamp to unchanged_file.
This solves the problem for me, and I've guarded it so it shouldn't break on
systems with no high-res timestamp. Please let me know if I can be helpful in
testing it further or making it more robust.
diff --git a/generator.c b/generator.c
index 3a4504f..2f64f5d 100644
--- a/generator.c...
2005 Jul 31
1
I think I found a bug...
I am looking at rsync 2.6.6
When I try to rsync a directory using --link-dest it
never creates hardlinks.
After crashing my way through the code here is what I
found:
generator.c: function 'unchanged_file'
if (ignore_times)
return 0;
return cmp_modtime(st->st_mtime, file->modtime) ==
0;
shouldn't these lines be:
if (ignore_times)
return 1;
return cmp_modtime(st->st_mtime, file->modtime) >=
0;
Or do I not understand something...
Nathan Bull...
2007 Oct 30
3
Rsync hard-links devices with different mtimes despite -t: expected?
I noticed that rsync is happy to hard-link a device node from a
--link-dest dir even if its mtime differs from that of the source device
node and --times is given. Is this behavior expected? It seems to
break the rule that a difference in preserved attributes disqualifies a
hard link.
To see the behavior, run the following as root:
mkdir src dest basis
mknod src/null c 1 3
sleep 1
mknod
2016 Jul 25
2
[Bug 12036] New: Multiple --link-dest, --copy-dest, or --compare-dest flags produce incorrect behavior
https://bugzilla.samba.org/show_bug.cgi?id=12036
Bug ID: 12036
Summary: Multiple --link-dest, --copy-dest, or --compare-dest
flags produce incorrect behavior
Product: rsync
Version: 3.1.2
Hardware: All
OS: Linux
Status: NEW
Severity: normal
Priority: P5
Component:
2013 Jan 22
0
rsync - using a --files-from list to cut out scanning. How to handle deletions? (fwd)B
...ion 3.1.0. (At our site, we use a patched version of rsync
which links a file from the link-dest directory rather copying from
source when a file is identical in the source and link-dest directory,
but exists and is different in the destination.)
I was not aware of the issue in the case where the unchanged_file() test
is passed, but not the unchanged_attrs() test, and the potential for
over-writing the attributes in not just the destination, but for all
hard-linked files.
This means that recycling directories, which as Teodor Milkov noted:
> "Such a behaviour (unlink changed files and then har...
2013 Jan 23
0
Changed attributes for a file in destination that is hard linked get propagated to --link-dest directories
...create a new copy of the file and attrs
# from the source, but could copy the file in the destination
# and update attrs, and remove the old file
else
# current behaviour
update just the attributes
endif
endif
Or, in the terms used in previous posts:
if ( destination unchanged_file() is true and unchanged_attrs() is false)
....
The test on the link-count is done, since teh new behaviour is needed
only when the target file has a link-count greater than 1.
Regards
Rob. Bell e-mail: Robert.Bell at csiro.au
--
Dr Robert C. Bell, BSc (Hons) PhD
Technical Services...
2008 May 08
1
Patch to not modify files in place unless "--inplace" option specified
...if ((iflags & ITEM_REPORT_CHANGE) && code != FNONE && verbose)
rprintf(code, "%s\n", fname);
#ifdef SUPPORT_HARD_LINKS
if (preserve_hard_links && F_IS_HLINKED(file))
@@ -1776,13 +1800,31 @@
else if (fnamecmp_type == FNAMECMP_FUZZY)
;
else if (unchanged_file(fnamecmp, file, &sx.st)) {
+ /* fnamecmp == fname, fnamecmp_type == FNAMECMP_FNAME */
+ int iflags = 0;
+
if (partialptr) {
do_unlink(partialptr);
handle_partial_dir(partialptr, PDIR_DELETE);
}
- set_file_attrs(fname, file, &sx, NULL, maybe_ATTRS_REPORT);
+ if (inplace) {...