search for: davegradwell

Hi, As far as I can see, the only way you can tell it's been a dry-run at the receiver-side, is to parse RSYNC_ARGs in the pre-xfer script. I think the only way is to crawl through the RSYNC_ARGs to find a value which: - starts with a single dash, and; - contains 'n', and; - comes prior to the "." value, signifying the start of the 'path args' (which seem inherently

...en --debug=exit Product: rsync Version: 3.1.1 Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P5 Component: core AssignedTo: wayned at samba.org ReportedBy: davegradwell at yahoo.co.uk QAContact: rsync-qa at samba.org It would be much appreciated if rsync could mark exits of dry-runs specifically as such. Example: 2014/09/06 10:22:41 [3449] [sender] _exit_cleanup(code=0, file=main.c, line=1165): about to call exit(0) (DRY RUN) My feeling is that a --dr...

...Summary: Bad time logging as daemon Product: rsync Version: 3.1.1 Platform: x64 OS/Version: Mac OS X Status: NEW Severity: normal Priority: P5 Component: core AssignedTo: wayned at samba.org ReportedBy: davegradwell at yahoo.co.uk QAContact: rsync-qa at samba.org When the rsync daemon logs, it fails to determine the correct time: 2014/08/18 18:47:24 [1002] connect from localhost (::1) 2014/08/18 17:47:24 [1003] rsync to dave/in-progress/data/ from dave at localhost (::1) When I specify use chroot =...

Hello, I am writing a backup application for Apple Macs which uses rsync at its core and I'd greatly appreciate any testing/feedback. It's detailed here: http://bonhardcomputing.com/backaroo/ you can download it here: http://bonhardcomputing.com/downloads/ and send any feedback to: info at bonhardcomputing.com (Please excuse the misuse of the rsync mailing list.) Regards, Dave.