similar to: [Bug 11521] New: rsync does not use high-resolution timestamps to determine file differences

I wrote on Fri, 02 Jan 2015 16:02:27 +0100: > --- a/generator.c 2014-06-14 01:05:08.000000000 +0200 > +++ b/generator.c 2015-01-02 15:50:30.000000000 +0100 > @@ -588,7 +588,14 @@ > if (ignore_times) > return 0; > - return cmp_time(st->st_mtime, file->modtime) == 0; > + return cmp_time(st->st_mtime, file->modtime) ==

On systems using nanoseconds differences should be taken into consideration. --- a/generator.c 2014-06-14 01:05:08.000000000 +0200 +++ b/generator.c 2014-12-25 11:19:54.000000000 +0100 @@ -588,7 +588,13 @@ if (ignore_times) return 0; - return cmp_time(st->st_mtime, file->modtime) == 0; + return cmp_time(st->st_mtime, file->modtime) == 0 +#ifdef ST_MTIME_NSEC + ?

Hi, I filed bug 11521 [1] back in August, and I can't tell if anyone's looked at it. It is a pretty rare, but easy to understand problem, with (I think) a straightforward fix. I included a reproducer script and a patch that worked well for me, but as this is the first time I've looked at the rsync code base I wouldn't be too surprised if I'd missed some portability

https://bugzilla.samba.org/show_bug.cgi?id=11635 Bug ID: 11635 Summary: make fails for out-of-tree build Product: rsync Version: 3.1.2 Hardware: All OS: All Status: NEW Severity: minor Priority: P5 Component: core Assignee: wayned at samba.org Reporter: andrey.gursky

https://bugzilla.samba.org/show_bug.cgi?id=10643 Summary: cmp_time() returns incorrect result due to integer overflow Product: rsync Version: 3.1.1 Platform: All OS/Version: All Status: NEW Severity: normal Priority: P5 Component: core AssignedTo: wayned at samba.org

https://bugzilla.samba.org/show_bug.cgi?id=11588 Bug ID: 11588 Summary: missing option: preallocate for all files except for sparse Product: rsync Version: 3.1.2 Hardware: x64 OS: Linux Status: NEW Severity: enhancement Priority: P5 Component: core

The existing APIs guestfs_stat, guestfs_lstat and guestfs_lstatlist return a stat structure that contains atime, mtime and ctime fields that store only the timestamp in seconds. Modern filesystems can store timestamps down to nanosecond granularity, and the ordinary glibc stat(2) wrapper will return these in "hidden" stat fields: struct timespec st_atim; /* Time of last

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 ---

https://bugzilla.samba.org/show_bug.cgi?id=12305 Bug ID: 12305 Summary: --fallocate and --sparse works wrong Product: rsync Version: 3.1.1 Hardware: All OS: Linux Status: NEW Severity: normal Priority: P5 Component: core Assignee: wayned at samba.org Reporter:

On a PPC machine running Mac OS X, I noticed that creation time is not preserved for files that are transferred (i.e. versus files that are not transferred, or files that have only attribute changes). I discovered two things that work together to cause this: 1) cmp_time (util.c) doesn't check for negative values provided in file1 or file2. If file2 is positive, and file1 is

It like we may have a bug in tar that ships with Centos. It looks like -o is mapped to --same-owner. Some basic info.... uname -a Linux jazzy 2.6.9-34.0.1.ELsmp #1 SMP Wed May 24 08:14:29 CDT 2006 i686 i686 i386 GNU/Linux cat /etc/redhat-release CentOS release 4.3 (Final) % /bin/tar --version tar (GNU tar) 1.14 --same-owner try extracting files with the same ownership --no-same-owner

Hi. Here's a patch for copying the atimes of files when -t/--times is given. I bumped the protocol to 29 since it sends more data over the wire. It obviously does not send the atime if it's sending data to an older rsync version. It passes all the tests (including the added atime.test) for me on a: Linux Debian/3.0 gcc 2.95.4 (debian), glibc 2.2.5 system. Any questions/feedback? I

https://bugzilla.samba.org/show_bug.cgi?id=13044 Bug ID: 13044 Summary: On macOS 10.12.6 with the new Xcode 9, `make check` is full of failures Product: rsync Version: 3.1.2 Hardware: x86 OS: Mac OS X Status: NEW Severity: regression Priority: P5 Component: core

Hi OpenSSH developers, I'm using OpenSSH on a daily basis and I'm very pleased with the work you've done. I am contributing to some Open Source software hosted at Savannah https://savannah.nongnu.org/projects/tsp and we recently hit some sftp unexpected behavior: https://savannah.gnu.org/support/?105838 when using chmod sftp client command it appears that setuid / setgid bits are

Setup: samba 2.2.2 Solaris 8 Trying to print to a printer attached to an NT4/sp6a machine. Printer passes 'test print page' test on NT and is shared. Problem: An error occurs when the smbclient command is used: cat afile | smbclient \\\\tech223\\testprn -U username%password -P -c "translate;print -" The error reported is "ERRDOS - ERRbadaccess (Invalid open mode.)

Hi, I searched whole 2007-2008 mailing lists for answer but couldn\'t find. I think it\'s easier and quicker to ask here. Suppose I have a message saved in file /tmp/afile. How can I tell deliver to deliver it to user\'s abc at domain.com mail box SPAM? I tried two following ways but no success: 1. more /tmp/afile | deliver -d abc at domain.com -m SPAM 2. deliver -d abc at

Esteemed R users and developers, How does one 'programatically' list or call objects for use in a function? For example, i thought i could do something better than this: save(A.cwb, B.cwb, C.cwb, D.cwb, E.cwb, F.cwb, file="afile.RData") with something like these- prfxs <- c("A", "B", "C", "D", "E", "F") #**

Hello list The Samba Howto Collection repeatedly asserts that by setting the sticky bit on directories any files created in those directories will be created with the owner set to that of the directory (for example, see http://samba.mirror.ac.uk/samba/docs/man/howto/AccessControls.html#id2541262). This has never worked for me. Files created inherit the group of the directory, but not the owner.

I posted a patch a few days ago that adds copying of atime. At that time, it was just enabled with -t/--times. After some time, we have figured out that that choice might not have been the best. Here's a new version of the patch (relative to CVS) that adds -A/--copy-atime instead. It also includes a test case. Any feedback on this patch and/or the previous one that I posted?

On Wed 20 Jan 2016, Andrey Gursky wrote: > > I was just about to implement the same, since nanoseconds are taken > into account when transferring, thus making it obvious not to ignore Really? I thought the protocol only transmits seconds. Paul