similar to: [PATCH] Add --preserve-atime switch to rsync

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

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?

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=1764 Summary: dry-run does not show changes in owner / group, permission, or timestamp Product: rsync Version: 2.6.3 Platform: All OS/Version: All Status: NEW Severity: normal Priority: P3 Component: core AssignedTo: wayned@samba.org

Bradley, and the rsync development team, I came across the following message on the rsync bug tracking system, while searching for just this feature (access time preservation)... http://rsync.samba.org/cgi-bin/rsync/incoming?id=2509;expression=atime;user=guest ... where it is written... > Date: Mon, 7 Feb 2000 02:59:42 -0500 > From: "Bradley M. Kuhn" <bkuhn@ebb.org> >

Hi, first of all, sorry for taking so long. Unfortunately, some other tasks kept coming up. Anyway, attached is the version of the flags patch, that is based on the one I'm using with 2.6.9. It is against the rsync-3.0.0pre9 release. I've included the option name change from the repository, so the option is now called --fileflags. Improved from the previously distributed version is the

Hi Everyone, The following feature request was received by a Debian user; could you comment on it? I think this seems reasonable, but perhaps should be enabled only conditionally (as if the argument parser isn't stressed enough). Thanks, Justin On Fri, Jul 23, 2004 at 05:09:09PM -0300, Pedro Zorzenon Neto wrote: > Package: rsync > Version: 2.6.2-2 > Severity: wishlist > Tags:

Strict C99 compilers do not support implicit function declarations or implicit ints, so something like the patch below is needed. Thanks, Florian diff --git a/configure.ac b/configure.ac index 4f68e98a..b5c7a582 100644 --- a/configure.ac +++ b/configure.ac @@ -173,6 +173,9 @@ AC_RUN_IFELSE([AC_LANG_SOURCE([[ #include <fcntl.h> #include <sys/types.h> #include <sys/wait.h>

Dear collegaues, please evaluate the patch attached, which allow to use both --detect-renamed and --fileflags extra features. This is meta-patch which sould be applied to detect-renamed. fileflags patch should be applied first, following by the modified detect-renamed patch. It is included in current FreeBSD port, but it seems it would be much more useful to be supported by samba

Looking at http://rsync.samba.org/ftp/rsync/patches/fileflags.diff -- It looks like the changes from fileflags-fixes.diff patch were applied to the patch from http://rsync.samba.org/ftp/rsync/rsync-patches-3.0.0.tar.gz , but this entire chunk of the that original diff file was lost: > diff -up a/config.h.in b/config.h.in > --- a/config.h.in > +++ b/config.h.in > @@ -64,6 +64,9 @@

Hello, as of gcc v2.7.2.1, the noreturn attribute needs to be given *after* the prototype declaration and not before, but for gcc v3.x, things changed for this attribute again, since gcc v2.5.x did it the way, newer gcc versions prefer it... I've applied a small unified diff, fixing this stuff. THX for listening. CU Tom. (Thomas M.Ott) Germany -------------- next part -------------- ---

I have users running rsync 3.0.6 on Mac OS 10.5 and 10.6 with the following arguments (for example): rsync -aNHAXx --fileflags --force-change --no-inc-recursive --delete-during --filter="P _Archive*" --filter="P /*" --backup --backup-dir="_Archive_2010_March_07_22-27-43" / /Volumes/Backup I can't seem to figure out how make_bak_dir could be returning this error

We use rsync to update an nfs server. After an update, we noticed that a large number of clients didn't see the updated data. It took me a while to be able to reliably reproduce this problem, but it happens on old and new versions of rysnc. It also happens across all the platforms we use here (sun/linux/netapp). This shows the problem: [Note my home directory is NFS mounted]

Hi Folks, This is my first post on nut-upsdev. I would like to share a small patch to enable support for the Powercool PCRACK 1200VA ups. I found that the UPS uses megatec/krauler protocol but is sensitive to the USB buffer length passed to it in requests via usb_get_string(), and usb_get_string_simple(). If the buflen is greater than 102 then the ups will reply to requests but does not

Sorry about the noise guys. Below a significantly improved patch. The main difference is that all calls to usb_get_string_.. have been wrapped in a new function nut_usb_get_string()  that is implemented in libusb.c This was necessary in order to make the bufflen_fix available in libusb.c where usb_get_string() is called in libusb_open() This wrapper function mops up and hides all the work

------- start of forwarded message (RFC 934 encapsulation) ------- From: Joe Zbiciak <im14u2c@cegt201.bradley.edu> Approved: alex@bach.cis.temple.edu Sender: Bugtraq List <BUGTRAQ@netspace.org> To: Multiple recipients of list BUGTRAQ <BUGTRAQ@netspace.org> Subject: Buffer overflow in Linux''s login program Date: Sun, 22 Dec 1996 09:27:24 -0600 Reply-To: Joe Zbiciak

All callers of robust_rename() call copy_file() if EXDEV is received. This patch moves the copy_file() call into robust_rename(). Patch Summary: -12 +1 backup.c -15 +2 rsync.c -9 +33 util.c -------------- next part -------------- patchwork diff util.c --- util.c 2004-02-17 09:58:44.000000000 -0500 +++ util.c 2004-02-17 10:21:22.000000000 -0500 @@ -355,16 +355,40 @@

When I perform a rsync with backup I get 100's of: make_bak_dir mkdir "/export/giger.back.....eary/java/weka/gui" failed: File exists make_bak_dir mkdir "/export/giger.back....ary/java/weka/gui" failed: File exists make_bak_dir mkdir "/export/giger.back...ary/java/weka/gui" failed: File exists . . . My backup command is: rsync -q --backup

Hello, I use rsync for incrmental backups in the following way: rsync \ $EXCLUDE \ -e ssh \ --archive \ --numeric-ids \ --compress \ --relative \ --one-file-system \ --cvs-exclude \ --delete \ --delete-excluded \ --bwlimit=0 \ --backup \ --suffix='' \ --backup-dir=$BACKUP_ROOT/$BACKUP_HOST/${TODAY} \ $BACKUP_HOST_AND_PATH

Rare and intermittent message groups suggest a race condition ... ? Here's the pattern of messages: rsync: make_bak_dir mkdir <path> failed: File exists (17) rsync: keep_backup failed: <path> -> <path>: No such file or directory (2) rsync: stat <path> failed: No such file or directory (2) How rarely? We run a scripted rsync daily on ~50 personal computers and