delete without copy
I'm programming an aplication to remote backup using rsync. The user has the option to crypt the files before sending them, but that options is causing us a lot of problems. We can´t crypt the original content, so we do a temporal copy. The problem is we just cant copy all files at the same time if they are big enough, so if a folder is bigger tan a size prefixed by the user, we copy file by file, crypt the file, send it and delete the crypted copy. That way it's imposible to delete files removed from sourceIs there any way to run rsync to create a file list and just delete files not present at source?...but without sending diferences..that way I can send file by file, and after that compare clear folders at source against crypted folders at destiny and get files deleted Thank you very much -- To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
DO NOT REPLY [Bug 5300] New: --xattrs-exclude and --xattrs-exclude-from
https://bugzilla.samba.org/show_bug.cgi?id=5300 Summary: --xattrs-exclude and --xattrs-exclude-from Product: rsync Version: 3.0.0 Platform: All OS/Version: Linux Status: NEW Severity: enhancement Priority: P3 Component: core AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] QAContact: [EMAIL PROTECTED] Options to specify which xattrs to ignore while comparing copying files. It seems like it should be possible to use filename filtering infrastructure. -- Configure bugmail: https://bugzilla.samba.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the QA contact for the bug, or are watching the QA contact. -- To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
DO NOT REPLY [Bug 5300] --xattrs-exclude and --xattrs-exclude-from
https://bugzilla.samba.org/show_bug.cgi?id=5300 [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution||DUPLICATE --- Comment #1 from [EMAIL PROTECTED] 2008-03-03 06:31 CST --- *** This bug has been marked as a duplicate of 4573 *** -- Configure bugmail: https://bugzilla.samba.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the QA contact for the bug, or are watching the QA contact. -- To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
DO NOT REPLY [Bug 4573] Hide/protect filtering of xattrs by name
https://bugzilla.samba.org/show_bug.cgi?id=4573 [EMAIL PROTECTED] changed: What|Removed |Added CC||[EMAIL PROTECTED] --- Comment #1 from [EMAIL PROTECTED] 2008-03-03 06:31 CST --- *** Bug 5300 has been marked as a duplicate of this bug. *** -- Configure bugmail: https://bugzilla.samba.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the QA contact for the bug, or are watching the QA contact. -- To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
Re: delete without copy
On Mon, 2008-03-03 at 11:14 +0100, david reinares wrote: Is there any way to run rsync to create a file list and just delete files not present at source? Yes, there's a neat little trick that does this: pass --ignore-non-existing --ignore-existing to stop rsync from creating new files and from updating existing files. Matt -- To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
Re: congrats!
On Mar 2, 2008, at 10:13 AM, Wayne Davison wrote: On Sun, Mar 02, 2008 at 07:40:32AM -0500, Robert DuToit wrote: Indeed - it worked fine. I had forgotten that you changed the default behavior and that --force-schg would override that too. Thanks! In the final patch for 3.0.0 the option names are --force-change (to force both user and system), --force-uchange (for just user) and --force-schange (for just system). Hi Wayne, I did a lot of tests on Tiger and Leopard with this good patch and it seems it doesn't need the --force-change options.The bbouncer test comes up clean with or without it. Is that true? Or should we use those option just in case? Should we have the option? Rob PS Loving it! Also, concerning fifo and devices, if I used Mike Bombich's patch for those- I think you said there was a problem with that - it works but is there potential for trouble using it as is? The problem is that the change would ignore EPERM errors on files that should really be reported. The attached patch should fix things for you (I get all OKs out of bbouncer after applying this). The patch includes the *_APPEND change in rsync.h that I mentioned in my prior email, so weed that out if you've already applied that. ..wayne.. fileflags-fixes.diff -- To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
RE: Rsync 3.0.0 released
A new version of cwrsync including rsync 3.0.0 is now available from http://itefix.no/cwrsync Tev -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Wayne Davison Sent: 1. mars 2008 22:30 To: [EMAIL PROTECTED] Cc: rsync@lists.samba.org Subject: Rsync 3.0.0 released Yes, it's finally that time -- rsync 3.0.0 has been released. This is a feature release that also includes quite a few bug fixes. I'd like thank everyone who participated in the development and testing of rsync. I hope that you enjoy this latest version! The 3.0.0 version number is such a large bump up from 2.6.9 due to the addition of an incremental recursion scan (which helps a lot with large transfers) and the official arrival of several other new features, including ACL support, extended attribute support, filename character- set conversion, etc. To see a full summary of the changes since 2.6.9, visit this link: http://rsync.samba.org/ftp/rsync/rsync-3.0.0pre10-NEWS You can download the source tar file and its signature from here: http://rsync.samba.org/ftp/rsync/rsync-3.0.0.tar.gz http://rsync.samba.org/ftp/rsync/rsync-3.0.0.tar.gz.asc The patches directory was released in a separate tar file (optional): http://rsync.samba.org/ftp/rsync/rsync-patches-3.0.0.tar.gz http://rsync.samba.org/ftp/rsync/rsync-patches-3.0.0.tar.gz.asc ..wayne.. -- To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
--append option description in manpage typo
I just noticed, too late )-: --append This causes rsync to update a file by appending data onto the end of the file, which presumes that the data that already exists on the receiving side is identical with the start of the file on the sending side. Any files that are the same size or shorter on the receiving size are skipped. Files that do not yet exist on the receiving side are also sent, since they are considered to have 0 length. Implies --inplace, but does not conflict with --sparse (since it is always extending a file's length). s/receiving size are skipped/receiving side are skipped/ I'm still confused though... If files that are shorter on the receiving side are skipped, how is it possible that rsync updates a file by appending data onto the end? Presumably that appending of data takes place on the receiving side. However, if only files that are longer on the receiving side are transferred, then how can those files be transferred by appending data? Paul Slootman -- To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
PST Rsync Issues
Hi All, I have a 1.8GB PST file that is backed up every night from a cygwin install) and every night rsync transfers about 1.8GB of data for that file. It changes a bit, but for all intents and purposes the entire file is transferred. There are other files on this system that rsync more typically, so I'm fairly certain this isn't a switch or command error on the calling end. I have also verified that the PST is closed at the time of backup. I'm curious if PSTs are just un-rsyncable due to their makeup or if there is something I can do to pare down this transfer and subsequent storage. Any tips or ideas are welcome. Thanks, Jon -- To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
Re: --append option description in manpage typo
On Mon, Mar 03, 2008 at 03:34:30PM +0100, Paul Slootman wrote: If files that are shorter on the receiving side are skipped, how is it possible that rsync updates a file by appending data onto the end? Thanks. That should say that files that are the same size or longer on the receiving side are skipped. I've checked-in a fix. ..wayne.. -- To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
DO NOT REPLY [Bug 5301] New: rsync 3.0.0 copyright dates not updated to 2008
https://bugzilla.samba.org/show_bug.cgi?id=5301 Summary: rsync 3.0.0 copyright dates not updated to 2008 Product: rsync Version: 3.0.0 Platform: All OS/Version: All Status: NEW Severity: trivial Priority: P3 Component: core AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] QAContact: [EMAIL PROTECTED] rsync --version: rsync version 3.0.0 protocol version 30 Copyright (C) 1996-2007 by Andrew Tridgell, Wayne Davison, and others. Web site: http://rsync.samba.org/ ... Just noticed that the copyright date range does not yet include 2008 :) Trivial patch: --- options.c.orig 2008-02-18 19:48:20.0 -0500 +++ options.c 2008-03-03 10:19:19.0 -0500 @@ -259,7 +259,7 @@ rprintf(f, %s version %s protocol version %d%s\n, RSYNC_NAME, RSYNC_VERSION, PROTOCOL_VERSION, subprotocol); - rprintf(f, Copyright (C) 1996-2007 by Andrew Tridgell, Wayne Davison, and others.\n); + rprintf(f, Copyright (C) 1996-2008 by Andrew Tridgell, Wayne Davison, and others.\n); rprintf(f, Web site: http://rsync.samba.org/\n;); rprintf(f, Capabilities:\n); rprintf(f, %d-bit files, %d-bit inums, %d-bit timestamps, %d-bit long ints,\n, -- Configure bugmail: https://bugzilla.samba.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the QA contact for the bug, or are watching the QA contact. -- To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
DO NOT REPLY [Bug 5301] rsync 3.0.0 copyright dates not updated to 2008
https://bugzilla.samba.org/show_bug.cgi?id=5301 --- Comment #1 from [EMAIL PROTECTED] 2008-03-03 09:57 CST --- Created an attachment (id=3158) -- (https://bugzilla.samba.org/attachment.cgi?id=3158action=view) Update copyright in options.c -- Configure bugmail: https://bugzilla.samba.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the QA contact for the bug, or are watching the QA contact. -- To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
Re: PST Rsync Issues
Jon Watson wrote: I'm curious if PSTs are just un-rsyncable due to their makeup or if there is something I can do to pare down this transfer and subsequent storage. Any tips or ideas are welcome. Outlook PST files are effectively database files. They can be optionally compressed and encrypted. If either of these options are enabled, I'd say it would completely screw up rsync's potential to do a differential copy - i.e. you'd transfer the lot every time. Even if those options aren't enabled, it could be that the data is altered dramatically each time a change in Outlook occurs that it still screws up rsync. Basically PST (and OST) files don't play nicely with differential copy tools. Similarly, the new Office 2007 format (basically compressed XML files) and OpenOffice format won't play nicely either - as compressed == random data - and rsync won't see linear changes in them like it can in text files/etc. (hope there's nothing too incorrect in the above. I'm sure someone will shout at me if I'm wrong ;-) -- Cheers Jason Haar Information Security Manager, Trimble Navigation Ltd. Phone: +64 3 9635 377 Fax: +64 3 9635 417 PGP Fingerprint: 7A2E 0407 C9A6 CAF6 2B9F 8422 C063 5EBB FE1D 66D1 -- To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
rsync 3.0.0 apparently crashing when running a single-use daemon server process
The long story: http://bugs.debian.org/469172 The short story: it looks like client_info is NULL at compat.c:90, if I look at the strace and ltrace output supplied in the above URL. Perhaps someone can investigate further, I don't have much time this evening. Tomorrow I can look again Paul Slootman -- To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
Re: PST Rsync Issues
On 3/3/2008, Jason Haar ([EMAIL PROTECTED]) wrote: Basically PST (and OST) files don't play nicely with differential copy tools. They also get very unstable the closer to 2GB in size you get... I'd never let a PST file get over about 500MB - had too many problems when I did (don't use it any more, TBird rocks)... -- Best regards, Charles -- To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
Re: Rsync sending complete file?
Matt McCutchen-7 wrote: On Sat, 2008-03-01 at 12:51 -0800, Some user wrote: its installed and working but i have no idea what im doing wrong. The command i'm using: #rsync -rv /media/mir1/ /media/mir2/ Now this works, recursive and verbose. However it takes approx 2 minutes and the output at the end is: sent 734973140 bytes received 42 bytes 10888491.59 bytes/sec forgive me if im wrong but that means its sent 734973140 bytes... I thought rsync only sent the differences? I have looked through --help and found nothing, currently going through the 'man' but their examples are dead simple (using no more paramaters than mine) and only do changes, how come mine seems to do full file? (mir1 and mir2 are on same partition so same type) Rsync doesn't do delta transfers when the source and destination are both local because there's no point. See: http://lists.samba.org/archive/rsync/2007-September/018603.html Matt -- To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html Gotcha, thankyou very much Matt. :) (PS - I'm after doing this as a lot of my files are 2gig VM files, and I don't want the odd small config change to mean lots if usage on second drive, would rather the CPU get pushed than the HDD, CPU more convenient to replace lol). -- View this message in context: http://www.nabble.com/Rsync-sending-complete-file--tp15780743p15786569.html Sent from the Samba - rsync mailing list archive at Nabble.com. -- To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
Passed all tests with flying colors on Mac OS X 10.4.11 - synopsis of installation and testing
Awesome work Wayne. I have been following the various threads about running rsync 3.0.0 on MacOS X 10.4.11 and wanted to confirm that following all the various bits of advice yields a clean running rsync (as tested by backup bouncer). I am running MacOS X 10.4.11 on PPC. The following is a synopsis of my installation procedure (as gathered from the various emails in the archive) - note that I had trouble with crtimes.diff and went back to osx-create-time.diff. Please let me know if I have included anything spurious or missed something critical (though I am pleased that everything worked)... I downloaded the source (3.0.0 release) and the patches (as posted on the front page as of this morning). I then added the patch Wayne provided called fileflags-fixes.diff (not in the folder when I downloaded it anyway) patch -p1 patches/osx-create-time.diff patch -p1 patches/fileflags.diff patch -p1 patches/fileflags-fixes.diff ./prepare-source (spurious? it did not seem to do anything...) patch -p1 patches/backup-dir-dels.diff ./configure make make test sudo make install I then used backup bouncer to test the installation: cd into backup bouncer folder ./bbouncer create-vol Src ./bbouncer create-vol Dst ./bbouncer create /Volumes/Src sudo rsync -aHAX --force-change /Volumes/Dst/ /Volumes/Src/ Finally, I ran the tests ./bbouncer verify -d /Volumes/Src /Volumes/Dst Verifying:basic-permissions ... ok Verifying: timestamps ... Sub-test:modification time ... ok ok Verifying: symlinks ... ok Verifying:symlink-ownership ... ok Verifying:hardlinks ... ok Verifying: resource-forks ... ok Verifying: finder-flags ... ok Verifying: finder-locks ... ok Verifying:creation-date ... ok Verifying:bsd-flags ... ok Verifying: extended-attrs ... Sub-test: on files ... ok Sub-test: on directories ... ok Sub-test: on symlinks ... ok ok Verifying: access-control-lists ... Sub-test: on files ... ok Sub-test: on dirs ... ok ok Verifying: fifo ... ok Verifying: devices ... ok Verifying: combo-tests ... Sub-test: xattrs + rsrc forks ... ok Sub-test: lots of metadata ... ok ok - Everything looks great. Thanks to Wayne and all those who have tested and refined this. I confess I am one of the myriad freeloaders who have been sitting back waiting for all of you to do the heavy lifting. I am a frequent beta tester on many open source projects, but I just don't have the guts to participate in such testing on a backup utility/app. So, I am thrilled to have a fully functional, modern, backup app for my Mac without having gone through the heartaches inherent in participating in the testing. Cheers, Rob -- To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
DO NOT REPLY [Bug 5299] 2.6.9 client cannot receive files from 3.0.0 server
https://bugzilla.samba.org/show_bug.cgi?id=5299 --- Comment #2 from [EMAIL PROTECTED] 2008-03-03 15:37 CST --- I booted my Sidux LiveCD on the Windows system, and ran rsync 2.6.9 to fetch the same set of files, and got the same error messages as mentioned above. So I don't think it has anything to do with Cygwin. The files I'm copying are many gigabytes each; I tried some smaller files (in the 2-5Mb range) and they went across fine. So this seems to only happen with really big files. I'll keep experimenting and see if I can find a definite cutoff size. (Something tells me it's gonna be the infamous 2Gb or 4Gb.) Also, while still booted into Sidux, I upgraded to rsync 3.0.0 and tried my original file transfer again. This fixed the problem. So hurry up with the Cygwin port of 3.0.0! :-D -- Configure bugmail: https://bugzilla.samba.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the QA contact for the bug, or are watching the QA contact. -- To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
Re: rsync 3.0.0 apparently crashing when running a single-use daemon server process
On Mon, Mar 03, 2008 at 09:16:46PM +0100, Paul Slootman wrote: The short story: it looks like client_info is NULL at compat.c:90, if I look at the strace and ltrace output supplied in the above URL. No, looks like the problem is a NULL config_file var. If rsync had been called with --rsync-path=rsync --config=FILE, it would work. Sadly, my only attempt at an automated test passes in an explicit config file. I'll fix the NULL and look to get a test for this added. ..wayne.. -- To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
Re: Rsync sending complete file?
On Sun, 2008-03-02 at 03:05 -0800, Some user wrote: (PS - I'm after doing this as a lot of my files are 2gig VM files, and I don't want the odd small config change to mean lots if usage on second drive, would rather the CPU get pushed than the HDD, CPU more convenient to replace lol). If you could be more specific, I might be able to help you improve the performance in the way you desire. Are you keeping just one copy of the source files on the destination, or multiple copies over time? What kind of usage of the destination disk to you want to reduce: disk I/O traffic or space usage? Matt -- To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
3.0.1 Test Success MacOS X 10.4.11
I have also been eager to test bbouncer The latest source passes with flying colours! but make check finds some problems with xattrs if not run by sudo I have xattr in /usr/local/bin/ from the source found at: http://dev.bignerdranch.com/public/bnr/eXttra.zip What I did: cd /usr/local/Source rsync -av --exclude=.git/ rsync://rsync.samba.org/ftp/unpacked/rsync . rsync -av --exclude=.git/ rsync://rsync.samba.org/ftp/rsync/patches rsync cd rsync patch -p1 patches/fileflags.diff patch -p1 patches/crtimes.diff ./configure rsync 3.0.1dev configuration successful make make check - xattrs log follows Testing for symlinks using 'test -h' makepath /usr/local/Source/rsync/testtmp/xattrs/from/foo/bar makepath /usr/local/Source/rsync/testtmp/xattrs/chk/foo Running: /usr/local/Source/rsync/rsync -avX . '/usr/local/Source/ rsync/testtmp/xattrs/chk/' sending incremental file list file0 file1 file2 file4 foo/bar/ foo/bar/file5 sent 786 bytes received 121 bytes 1814.00 bytes/sec total size is 38 speedup is 0.04 - check how the directory listings compare with diff: - check how the files compare with diff: - --- /usr/local/Source/rsync/testtmp/xattrs/xattrs.txt 2008-03-03 21:24:32.0 +0100 +++ - 2008-03-03 21:24:32.0 +0100 @@ -12,13 +12,5 @@ user.foo foo user.long a long attribute for our new file that tests to ensure that this works foo/file3 - user.bar new bar - user.equal this long attribute should remain the same and not need to be transferred - user.foo new foo -user.long this is also a long attribute that will be truncated in the initial data send file4 foo/bar/file5 - user.bar new bar - user.equal this long attribute should remain the same and not need to be transferred - user.foo new foo -user.long this is also a long attribute that will be truncated in the initial data send - xattrs log ends FAILxattrs - overall results: 30 passed 1 failed 6 skipped overall result is 1 make: *** [check] Error 1 sudo make check . PASSwildmatch PASSxattrs - overall results: 33 passed 4 skipped overall result is 0 sudo make install cd /usr/local/Source/backup-bouncer-0.1.2/ ./bbouncer create-vol mysource ./bbouncer create-vol mybackup ./bbouncer create /Volumes/mysource/ sudo rsync -aHAXiP --fileflags --crtimes /Volumes/mysource/ /Volumes/ mybackup/ ./bbouncer verify -d /Volumes/mysource/ /Volumes/mybackup Verifying:basic-permissions ... ok Verifying: timestamps ... Sub-test:modification time ... ok ok Verifying: symlinks ... ok Verifying:symlink-ownership ... ok Verifying:hardlinks ... ok Verifying: resource-forks ... ok Verifying: finder-flags ... ok Verifying: finder-locks ... ok Verifying:creation-date ... ok Verifying:bsd-flags ... ok Verifying: extended-attrs ... Sub-test: on files ... ok Sub-test: on directories ... ok Sub-test: on symlinks ... ok ok Verifying: access-control-lists ... Sub-test: on files ... ok Sub-test: on dirs ... ok ok Verifying: fifo ... ok Verifying: devices ... ok Verifying: combo-tests ... Sub-test: xattrs + rsrc forks ... ok Sub-test: lots of metadata ... ok ok -- To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
Re: Passed all tests with flying colors on Mac OS X 10.4.11 - synopsis of installation and testing
I am running MacOS X 10.4.11 on PPC. The following is a synopsis of my installation procedure (as gathered from the various emails in the archive) - note that I had trouble with crtimes.diff and went back to osx-create-time.diff. Please let me know if I have included anything spurious or missed something critical (though I am pleased that everything worked)... I also get perfect results on 3.0.0 with both MacOS X 10.4.11 on PPC and MacOS X 10.5.2 on Intel, using fileflags.diff, crtimes.diff and Wayne's new fileflags-fixes.diff. I find it interesting that you have had no luck with crtimes.diff. Could you post your results? Are you applying the patches in the right order (that is, fileflags.diff followed by crtimes.diff, not vice versa)? I suspect the backup-dir-dels.diff patch is not strictly necessary, unless you actually want the functionality (as many of us do). ./prepare-source may or may not do anything, depending which source version you're using. Tony M. -- To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
Re: congrats!
I did a lot of tests on Tiger and Leopard with this good patch and it seems it doesn't need the --force-change options.The bbouncer test comes up clean with or without it. Is that true? Or should we use those option just in case? Should we have the option? Rob My guess is you don't need --force-change with the backup-bouncer tests because the destination volume is clean. If you were trying to replace existing files on the destination, then failing to include -- force-change would lead to problems if any files have 'uchg' or 'schg' flags set. Tony -- To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
Re: Passed all tests with flying colors on Mac OS X 10.4.11 - synopsis of installation and testing
I think you hit the nail on the head. I put the crtimes.diff first because I was simply swapping it in for osx-create-time.diff in Axel's email 3.0.0 test failure MacOS X 10.4.11. Upon invoking make, this error in the ordering of the patches, on my part yielded: Check the output of your 'patch' commands and make sure there are no FAILED messages. If there are, then your 'make' will probably fail unless they're resolved. If you apply fileflags.diff followed by crtimes.diff then you shouldn't see any failures - if you do then it's probably worth letting the list know. Tony M. -- To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
Re: rsync 3.0.0 apparently crashing when running a single-use daemon server process
On Mon, Mar 03, 2008 at 01:50:28PM -0800, Wayne Davison wrote:
I'll fix the NULL and look to get a test for this added.
The git repository has both the fix and the extended test.
Attached is just the NULL-pointer fix.
Thanks for your help!
..wayne..
--- a/clientserver.c
+++ b/clientserver.c
@@ -864,6 +864,17 @@ static void send_listing(int fd)
io_printf(fd,@RSYNCD: EXIT\n);
}
+static int load_config(int globals_only)
+{
+ if (!config_file) {
+ if (am_server am_root = 0)
+ config_file = RSYNCD_USERCONF;
+ else
+ config_file = RSYNCD_SYSCONF;
+ }
+ return lp_load(config_file, globals_only);
+}
+
/* this is called when a connection is established to a client
and we want to start talking. The setup of the system is done from
here */
@@ -879,7 +890,7 @@ int start_daemon(int f_in, int f_out)
* might cause log-file output to occur. This ensures that the
* log file param gets honored for the 2 non-forked use-cases
* (when rsync is run by init and run by a remote shell). */
- if (!lp_load(config_file, 0))
+ if (!load_config(0))
exit_cleanup(RERR_SYNTAX);
addr = client_addr(f_in);
@@ -988,13 +999,6 @@ static void become_daemon(void)
int daemon_main(void)
{
- if (!config_file) {
- if (am_server am_root = 0)
- config_file = RSYNCD_USERCONF;
- else
- config_file = RSYNCD_SYSCONF;
- }
-
if (is_a_socket(STDIN_FILENO)) {
int i;
@@ -1009,7 +1013,7 @@ int daemon_main(void)
return start_daemon(STDIN_FILENO, STDIN_FILENO);
}
- if (!lp_load(config_file, 1)) {
+ if (!load_config(1)) {
fprintf(stderr, Failed to parse config file: %s\n,
config_file);
exit_cleanup(RERR_SYNTAX);
}
--
To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync
Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
