DO NOT REPLY [Bug 7523] New: rsync exclude file ignores spaces
https://bugzilla.samba.org/show_bug.cgi?id=7523 Summary: rsync exclude file ignores spaces Product: rsync Version: 2.6.8 Platform: x86 OS/Version: Linux Status: NEW Severity: major Priority: P3 Component: core AssignedTo: way...@samba.org ReportedBy: dfwjim2...@yahoo.com QAContact: rsync...@samba.org Using the FAQ page at rsync, using tips on the commandline with --exclude= having spaces in the file-spec pattern for --exclude, seem to be ignored by --exclude-from inside the exclude file. I used all types of space escaping techniques: questionmark, single \, the triple \\\, combinations of single double quoting. the only way I can get the path to exclude is to cut it off at the first instance of space with a *, however this may cut off similarly named directories. This needs to be fixed. -- 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. -- Please use reply-all for most replies to avoid omitting the mailing list. To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
How can I make rsync not overwrite files that has not changed?
Sorry for asking this but I find the manpage to be a little confusing on this. I want rsync to only replace files that has acctually a different content, it should completely ignore any timestamps on files.. How can I make it behave like that? -- Please use reply-all for most replies to avoid omitting the mailing list. 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: How can I make rsync not overwrite files that has not changed?
Subject: How can I make rsync not overwrite files that has not changed? Sorry for asking this but I find the manpage to be a little confusing on this. I want rsync to only replace files that has acctually a different content, it should completely ignore any timestamps on files. -c, --checksum skip based on checksum, not mod-time size -- Bob Bagwill -- Please use reply-all for most replies to avoid omitting the mailing list. 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: RERR_PARTIAL exit status
On Thu, 2010-06-17 at 13:46 -0600, Keith Hellman wrote: I recently changed my backup script to invoke with rsync w/ -v -v and store the output to (yet another) log file. After a nightly backup I looked at the results, and: 1. removed all the lines ending in ' is uptodoate$' 2. removed all the lines with a space (presumably a log message causing RERR_PARTIAL would have a space in it) 3. removed all the lines w/ ' [-=] ' #3 may be the problem. Some RERR_PARTIAL error messages contain that sequence, for example, 'rename foo - bar: Operation not permitted'. I was hoping to weasel this log file down to that singlular file that is causing the RERR_PARTIAL exit code. No dice. All I saw were the 2 filenames I have with a space in them. :^( So, my questions to the rsync community are: 1. Am I correct in assuming that rsync *would* write something to stdout or stderr when the RERR_PARTIAL condition is triggered? Yes. If rsync exits with RERR_PARTIAL without printing a specific message about the problem to stderr, it's a bug. I would suggest sending stdout and stderr to separate files, like this: rsync ... rsync.out 2rsync.err Then look at rsync.err. It should have the relevant errors and nothing else. If it is empty, then something deeper is wrong and it may be helpful to strace rsync. -- Matt -- Please use reply-all for most replies to avoid omitting the mailing list. 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 7523] rsync exclude file ignores spaces
https://bugzilla.samba.org/show_bug.cgi?id=7523 way...@samba.org changed: What|Removed |Added Status|NEW |RESOLVED Resolution||WORKSFORME --- Comment #1 from way...@samba.org 2010-06-19 00:28 CST --- This works fine. There is no need for any escaping inside an exclude-from file since spaces have no special meaning (apart from the plus/minus prefixes that are separated by a single space). -- 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. -- Please use reply-all for most replies to avoid omitting the mailing list. 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: Prevent --max-delete from deleting any files?
On Wed, Jun 2, 2010 at 10:30 AM, Marco Moreno mmor...@pobox.com wrote: Is there a way to prevent rsync from deleting any files if --max-delete is exceeded? No, there is no way to do that. You could tweak the source to change --delete-delay so that it ignores the delay list if the list grows too long, but that is not something that is currently supported. ..wayne.. -- Please use reply-all for most replies to avoid omitting the mailing list. 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: change of behaviour on rsync -R and top level symlinks?
On Wed, Jun 16, 2010 at 1:37 PM, Marc MERLIN m...@merlins.org wrote: I should keep my /a - /c symlink on the destination without --no-implied-dirs since I have /a - /c on the source too, and this is what rsync 2 did. See the --relative option in the man page: Beginning with rsync 3.0.0, rsync always sends these implied directories as real directories in the file list, even if a path element is really a symlink on the sending side. This prevents some really unexpected behaviors when copying the full path of a file that you didn’t realize had a symlink in its path. If you want to duplicate a server-side symlink, include both the symlink via its path, and referent directory via its real path. If you’re dealing with an older rsync on the sending side, you may need to use the --no-implied-dirs option. So, in your case, you're wanting to both duplicate the /a symlink, and something down in the /c heirarchy, so you could copy both /a (the symlink) and /c/b (the real hierarchy) in the same transfer. Or just use --no-i-d, as you discovered. ..wayne.. -- Please use reply-all for most replies to avoid omitting the mailing list. To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
