similar to: Ignoring parts of stat(2)

Hello, I'm trying to do something that did not sound difficult, but no option I've tried seems to be working. I apologize in advance if I'm missing something obvious. I need to sync only directories from one tree to a similar, but older tree *without* updating the modtimes of directories that already exist in the destination. Or phrased the other way, I want to entirely skip

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

Hi All, I'm trying a remote backup for the first time. It is between two laptops, I installed rsync 3.0.7 on both compiled patch -p1 <patches/fileflags.diff patch -p1 <patches/crtimes.diff patch -p1 <patches/crtimes-64bit.diff patch -p1 <patches/crtimes-hfs+.dif f patch -p1 <patches/hfs_compression.diff ./configure make this all works perfectly for local backups, clones

Hello all, we are experiencing problems with samba 2.0.6 and the MKS touch command. during our builds, we touch files and directories so that our make dependencies work correctly. Unfortunately, it seems that MKS' touch.exe doesn't actually change the time stamp of a file or directory. The command returns without an error, but the timestamp does not change. The same problem exists

Since there has been a recent tweak to the functionality of Sys.setFileTime() I thought it might be an opportune time to ask a question regarding the decision to set both access and modification times (i.e. settime.actime = settime.modtime = (int)ftime; ) vs provide a parameter for each. Might it be possible to change the behavior to accept two parameters (one for active and one for modtime) but

Whenever you use --times (included in --archive) rsync will fix incorrect time stamps. The only thing --size-only is doing is keeping the incorrect data instead of replacing it. The purpose of these options is to "fix" a copy done in a way that did not preserve timestamps but the data is known to have not changed. These options allow rsync to correct the incorrect timestamps without

When a file of same length already exists at the destination then the command 'rsync --archive --size-only' (--archive is same as -rlptgoD) may change the modification time of the destination file even if no modification was made. Type the following commands in a terminal in order to reproduce the problem: $ mkdir source $ mkdir target $ echo "file one" > source/file $

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

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?

In the past there have been discussions about adding a switch to rsync to preserve the atime on files being copied by rsync. I needed this function for a project I'm working on and decided to invent it. I've attached the diffs. Note that this has the limitations describe in previous emails, namely that preserving atime causes ctime to not be preserved. *** Patch follows *** ***

I'm implementing this right now. BY_HANDLE_FILE_INFORMATION isn't the correct API, as Path doesn't have an open file handle handy. Nor does it need one. Reid Spencer wrote: >Henrik, > >modTime.fromWin32Time(ftLastWriteTime); > Note that you'll need write a "fromWin32Time" for the TimeValue > class to make the conversion of ftLastWriteTime to

Dear Martin Pool. We regularly use rsync for making backups of our file systems but we have noticed that the atimes are not transferred with the files and are also always updated on the sender's side. Therefore, we have created a modified version of rsync based on rsync-2.6.6 protocol version 29 which transfers the access times with the transferred files and also allows to preserve the access

Henrik, modTime.fromWin32Time(ftLastWriteTime); Note that you'll need write a "fromWin32Time" for the TimeValue class to make the conversion of ftLastWriteTime to TimeValue's notion of normalized time. isDir = dwFileAttributes & FILE_ATTRIBUTE_DIRECTORY; fileSize = nFileSizeLow + (nFileSizeHigh << sizeof(DWORD)*8); The mode, user, and group fields aren't

Hi. rsync 3.0.8 FreeBSD RELENG_4 i386. rsync -Haxi --delete /.../ /.../ The first pathspec above (residing on zz, a full filesystem) is: /vvvv/wwww/xxxx/zz/ The second pathspec above (residing on yyy, an empty filesystem) is: /vvvv/wwww/xxxx/yyy/zz/ It's obviously a 'copy everything over' operation. I've had to obfuscate the pathnames, however the exact pathlength throughout

How exactly does rsync determine that the copy has the incorrect timestamp and not the source file? Does it assume that the copy must be incorrect or are there other criteria that have to be considered? Quoting Kevin Korb via rsync <rsync at lists.samba.org>: > Whenever you use --times (included in --archive) rsync will fix > incorrect time stamps. The only thing --size-only is

Dear developers, In the rsync's manpage, there is a line describing the "archive mode" option: -a, --archive archive mode; equals -rlptgoD (no -H,-A,-X) Archive mode means that all data is backed up sensibly while the same doesn't apply for all metadata (hence the mentioned -H, -A and -X options). There is another similar "special file system option" as

Okay. Sounds good. Look forward to it. Reid On Mon, 2004-12-13 at 20:34, Jeff Cohen wrote: > I'm implementing this right now. BY_HANDLE_FILE_INFORMATION isn't the > correct API, as Path doesn't have an open file handle handy. Nor does > it need one. > > Reid Spencer wrote: > > >Henrik, > > > >modTime.fromWin32Time(ftLastWriteTime); > >

--- man/flac.1 | 25 +++++++++++++++++++++---- man/flac.sgml | 2 ++ 2 files changed, 23 insertions(+), 4 deletions(-) diff --git a/man/flac.1 b/man/flac.1 index fef4ded..3d7bd50 100644 --- a/man/flac.1 +++ b/man/flac.1 @@ -68,6 +68,9 @@ Prefix each output file name with the given string. This can be useful for enco \fB--delete-input-file \fR Automatically delete the input file after

Hi all. I have a strange issue with sync'ing from a USB-attached ext4 file system on one machine, to a USB-attached ext3 file system on another. The sync works fine (a few thousand files). If I run it again straight away, or a few minutes later, rsync reports no action required. But if I wait for a few hours and run it again it copies all the files again. I'm trying to determine

Patch to add an archive mode that includes deletion. -Rob -------------- next part -------------- Adds an archive mode that includes the delete option. --- orig/options.c 2004-09-23 13:39:05.000000000 -0400 +++ options.c 2004-11-13 09:56:27.000000000 -0500 @@ -39,6 +39,7 @@ int whole_file = -1; int archive_mode = 0; +int archive_delete_mode = 0; int keep_dirlinks = 0; int copy_links = 0;