Include and Exclude
Hi guys, actually with this command: rsync -avzHP --include "3.4/" --include "3.4/**" --include "4.0/" --include "4.0/**" --exclude "*" --bwlimit=30 rsync.example.foo::packages/centos/* . i correctly rsync only 3.4 and 4.0 dirs of repository... I would like to rsync only dirs "xxx" and "yyy" from 3.4 and 4.0, for example: /packages/centos/3.4/someone/xxx/ - yes /packages/centos/3.4/someone/ - no /packages/centos/4.0/someone/xxx/ - yes /packages/centos/4.0/sometwo/yyy/ - yes Is it possible? Thank you, fRANz -- 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 error: some files could not be transferred -- How to ignore
Title: Message Hello all, I'm using rsync client in Linux box and cygwin rsync daemon in Win 2k machine. When i do transfer of directory contents "C:/Documents And Settings/Administrator/Local Settings/Application Data/Microsoft/Windows" using rsync, i'm getting the following error through stderr. rsync: send_files failed to open "ion Data/Microsoft/Windows/UsrClass.dat" (in C:_Documents And Settings_Administrator_Local Settings_Application Data_Microsoft_Windows): Device or resource busy (16) rsync: send_files failed to open "ion Data/Microsoft/Windows/UsrClass.dat.LOG" (in C:_Documents And Settings_Administrator_Local Settings_Application Data_Microsoft_Windows): Device or resource busy (16) rsync error: some files could not be transferred (code 23) at main.c(1045) -- When i manually checked, the files UsrClass.dat and UsrClass.dat.LOG are not accessible. Probably the error comes because of this. Is there any way to ignore these errors when i do file transfer using rsync? Thanks, Sanal Confidentiality Notice The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain confidential or privileged information. If you are not the intended recipient, please notify the sender at Wipro or [EMAIL PROTECTED] immediately and destroy all copies of this message and any attachments. -- To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
using rsync on files that are being written to
I know people who shutdown the services on their *nix box before backing up with rsync. this is to avoid accidentily backing up files that are being written to, which might result in a corrupt backup of that file. is this even a concern? if it is, what methods are available for a small shop to schedule regular backups but still maintain uptime? thanks! -- 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: handling duplicate names deterministically and adding alternative checksum algorithms
Thanks for the pointer to that mergesort thread and for the md5 patch. Is rsync going to stick with qsort as the default sorting algorithm? Would a patch to add a --mergesort option be accepted? Even though most of my boxes are Linux and it appears that qsort usually runs as a mergesort, I would still like an option to enforce it so I don't get suprised one day when an actual qsort is used due to memory contention. And what would be the chances of a --sha1 option patch being accepted? Thank you again, Andrew On 6/13/05, Wayne Davison <[EMAIL PROTECTED]> wrote: > On Thu, Jun 09, 2005 at 05:24:45PM -0600, Andrew Shewmaker wrote: > > Our current practices would benefit if rsync were enhanced to handle > > duplicate names deterministically as described in the todo list. > > One proposed solution to this was to use a functioned called > mergesort(). A patch was provided that includes a compatibility > function for systems that don't include mergesort(): > > http://lists.samba.org/archive/rsync/2004-August/010398.html > > > we would also be interested in the ability to optionally use a > > stronger checksum algorithm. > > I just put a diff into the patches dir that implements the --md5 option > (extracted and cleaned up from a larger patch set that was sent to me by > Wolfgang Neuman): > > http://rsync.samba.org/ftp/unpacked/rsync/patches/md5.diff > > As you'd expect, this tells rsync to use MD5 checksums instead of MD4. > > ..wayne.. > -- Andrew Shewmaker -- 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: handling duplicate names deterministically and adding alternative checksum algorithms
On Thu, Jun 16, 2005 at 02:01:54PM -0600, Andrew Shewmaker wrote: > Is rsync going to stick with qsort as the default sorting algorithm? Yes. I don't wish to increase the memory use for really large file sets that have no need for deterministic unduplication. > Would a patch to add a --mergesort option be accepted? It could at least go in the patches dir, and I would also consider applying it to the trunk. > And what would be the chances of a --sha1 option patch being accepted? I think that would be something useful. ..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: logging
On Wed, Jun 15, 2005 at 11:55:29PM -0400, sc0ri0n wrote: > I do not see a parameter to specify a log file. Why would that be? That all depends on what you're expecting. See the rsyncd.conf manpage for how to make the daemon log to a file. No other log-file output is directly supported (e.g. for a remote-shell transfer), but you can use the --log-format option and redirect (or tee) the output to a file. ..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: Include and Exclude
On Thu, Jun 16, 2005 at 10:00:07AM +0200, fRANz wrote: > rsync -avzHP --include "3.4/" --include "3.4/**" --include "4.0/" > --include "4.0/**" --exclude "*" --bwlimit=30 > rsync.example.foo::packages/centos/* . An easier way to do this is to use: --include=/3.4/ --include=/4.0/ --exclude='/*' That anchors the dirs and the wildcard so that they only apply to the root of the transfer (making the ** includes unnecessary). Also, you are usually better off just using a trailing slash at the end of a directory arg instead of specifying a '*' after it. > I would like to rsync only dirs "xxx" and "yyy" from 3.4 and 4.0, for example: > > /packages/centos/3.4/someone/xxx/ - yes > /packages/centos/3.4/someone/ - no > /packages/centos/4.0/someone/xxx/ - yes > /packages/centos/4.0/sometwo/yyy/ - yes This works in a similar way to the example above -- specify what you want to include at a particular level, and then exclude everything else at that level. As long as the source arg contains "/packages/centos/", your include/exclude rules would look like this (I'm switching to the exclude file format): + /3.4/ + /3.4/someone/ + /3.4/someone/xxx/ - /3.4/someone/* - /3.4/* + /4.0/ + /4.0/someone/ + /4.0/someone/xxx/ - /4.0/someone/* + /4.0/sometwo/ + /4.0/sometwo/yyy/ - /4.0/sometwo/* - /4.0/* - /* Another solution might be to use --files-from combined with -r. Since the --relative option gets turned on, the paths from the args gets used in the destination. Put this in a file "mylist": /3.4/someone/xxx /4.0/someone/xxx /4.0/sometwo/yyy And then run this: rsync -avzHPr --files-from=mylist --bwlimit=30 host::packages/centos/ . ..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 error: some files could not be transferred -- How to ignore
On Thu, Jun 16, 2005 at 08:49:54PM +0530, [EMAIL PROTECTED] wrote: > Is there any way to ignore these errors when i do file transfer using > rsync? What do you mean by ignore? They're just warnings, so rsync ignores them already for most things, just not deletions that happen after the warnings (such as --delete-after), but see the --ignore option to handle that. If you mean that your script halts, you can code a script to ignore only specific return codes (namely code 23). One would need to know what shell you're using to help with that. ..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
