Re: Rsync failed to set times (on temporary files)
In , on 01/24/21 at 07:46 PM, Leon Vanderploeg via rsync said: Hi, >rsync: failed to set times on "//.ImageTest.reg.jDGIg0": >Invalid argument (22) >Where is temp file coming from? They are created to hold the content of the file to be replaced during the data transfer. The names are chosen to minimize the change of naming comflicts. This is rsync's default behavior. >Why is the set time failing? Hard to say without more information. Exactly what is the failing rsync command line? What is the destination file system format? Are you running the same version of rsync on both sides of the transfer? Different platforms have different rules for timestamp granularity. This may or many not be contributing to this issue. Steven -- ---------- "Steven Levine" Warp/DIY/BlueLion etc. www.scoug.com www.arcanoae.com www.warpcave.com -- -- 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: Operation not supported (95)
In <20160623205843.GB6633@kw.merryville>, on 06/23/16 at 11:58 PM, Albert Berger <nbds...@gmail.com> said: Hi, >I did some search about this error before asking this question, and in >other case unsupported ACLs were indeed the cause. But btrfs supports >ACLs: In addition to what Kevin said, if you are rsync-ing to a SAMBA share, you will be limited to what the SAMBA server supports and not all are configured to enable ACL support. >[root@kw al]# getfacl /mnt/backup/rootdir/var/log/journal/remote getfacl: This implies that the ACLs can be read, but it says nothing about whether the local system has the rights to delete the default ACLs from var/log/journal/remote. You need to test this with something like setfacl --remove-default \ /mnt/backup/rootdir/var/log/journal/remote Steven -- ------ "Steven Levine" <stev...@earthlink.net> Warp/DIY/BlueLion etc. www.scoug.com www.arcanoae.com www.warpcave.com -- -- 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: rsync keeps writing files over
In <d37e24fa.120d%mcdowe...@si.edu>, on 06/09/16 at 12:17 AM, "McDowell, Blake" <mcdowe...@si.edu> said: Hi Blake, Please reply to the list. >rsync -nri --modify-window=1 As others mentioned, you need need to use --times. This is needed so that we can see use output from --itemize-changes. >Gives me the following for most files >f..T... >2015_167_1_1__Boy_What_A_Girl_R2/2015_167_1_1__Boy_What_A_Girl__UHD_DPX_R2/ >BWAG_R2_00138428.dpx >Although a few have >f..T..n >2015_167_1_1__Boy_What_A_Girl_R2/2015_167_1_1__Boy_What_A_Girl__UHD_DPX_R2/ >BWAG_R2_00135909.dpx At a certain level this makes sense. Without --times, the timestamps are not used to determine whether or not a file needs to be transferred and, in addition, the receiver will set the timestamp to the current time on the receiver. This is what the docs mean when they say "Note that if this option is not used, the optimization that excludes files that have not been modified cannot be effective;" >(I¹m not quite sure I completely understand -modify-window) You should not need --modify-window. Modify window is needed when the source and destination file systems have differing timestamp resolutions. For example if transferring to a Window's filesystem that had 2-second timestamp resolution from a *ix system with 1-second resolution, you would need to use --modify-window=2 to avoid spurious transfers. >Here is a file example of timestamps as rsync interprets them: >-rwxrwxrwx 24,839,552 2016/06/08 13:13:19 BWAG_R2_00086400.dpx >Here is a file example of timestamps as rsync interprets them: >-rwxrwxrwx 24,839,552 2016/05/27 13:43:32 BWAG_R2_00086400.dpx Without --times, this is the expected behavior. The timestamps differ, so rsync will transfer the file. Because the file content is the same, the transfer will be quick, but a tranfer will happen. If you cannot use --times, you many need to use some combination of --update and --ignore-times an possibly --size-only to avoid selecting these files for transfer. Exactly which options will be approriate will depend on the content of your files and how the content changes. FWIW, if --times cannot set the timestamp correctly on the receiver, I would suspect an issue with the filesystem or your rsync build. Rsync uses the standard platform APIs for setting the timestamps so this should just work. >But, for the files that have the ³n² What "n" do you mean? Another FWIW, when testing, --dry-run (i.e. -n) is useful to understand which files will be transferred, especially when working with complex filters, but you need to run without -n to see that true results of the transfer. Steven -- -- "Steven Levine" <stev...@earthlink.net> Warp/DIY/BlueLion etc. www.scoug.com www.arcanoae.com www.warpcave.com -- -- 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: Deletion of destination files
In <87bn3frk92@gmail.com>, on 06/05/16 at 10:40 AM, Rodolfo Medina <rodolfo.med...@gmail.com> said: Hi Rodolfo, > $ rsync --dry-run -vrt --delete --modify-window=1 file1 file2 file3 ... >/mnt/pendrive/rodolfo >not happen. In rsync `man' page I can't find a solution. It comes up so often on the list that this should be a FAQ. Check out --itemize-changes It is almost always the best solution for understanding why rsync is processing a given file a certain way. --verbose is typically more helpful when diagnosing problems with complex filters and other obscure problems. Steven -- ---------- "Steven Levine" <stev...@earthlink.net> Warp/DIY/BlueLion etc. www.scoug.com www.arcanoae.com www.warpcave.com -- -- 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: rsync keeps writing files over
In <d3762d63.17a7%mcdowe...@si.edu>, on 06/02/16 at 10:42 PM, "McDowell, Blake" <mcdowe...@si.edu> said: Hi Blake, >The storage is just an regular HDD in a mac pro tower. I can t imagine >why it wouldn t handle timestamps. Also of note - this problem doesn t >exist for every file, just the vast majority. So, that just makes it more >confusing. Are the file systems the same on the source and the destination partitions? Check out --modify-window in the help. If the source and destination file systems have different timestamp precision, this is the usual solution. You can also try rsync /path-to-foo where path-to-foo is a directory or file. This will list the file timestamps as rsync interprets them. BTW, what version of rsync are you running? It might matter. Steven -- ---------- "Steven Levine" <stev...@earthlink.net> Warp/DIY/BlueLion etc. www.scoug.com www.arcanoae.com www.warpcave.com -- -- 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: Delete remote folder
In <20160602082722.8F11829233B7@macserver.private>, on 06/02/16
at 10:27 AM, Fabian Cenedese <cened...@indel.ch> said:
Hi Fabian,
>rsync -a --delete empty_local_folder remote_folder_to_delete
>to get rid of the contents. However the folder itself still remains. So
>after a while I'd have a lot of empty folders.
This comes up on the list every now and then.
Here's a snip from an archive message:
Here is how you would write an "rsyncrm" script that can be invoked like
"rsyncrm -ni remote::volume/directory". Note that this reveals the
attributes of the current directory to the server.
#!/bin/bash
victim="${@: -1:1}"
rsync -d --del --filter="R /$(basename -- "$victim")" --filter='- /*' \
"${@:1:$#-1}" . "$(dirname -- "$victim")"
This works because it deletes the unwanted directory from the parent
directory.
Steven
--
--
"Steven Levine" <stev...@earthlink.net> Warp/DIY/BlueLion etc.
www.scoug.com www.arcanoae.com www.warpcave.com
--
--
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: rsync with overlay tree
In <b4e1ec5d-5e46-4a98-9018-c5e4c4441...@equalit.ie>, on 03/31/16 at 03:40 PM, tomr <t...@equalit.ie> said: Hi, >Then I'd run an rsync like: >rsync -av --overlay /path/to/sync/groupN \ > /path/to/sync/common remotehost: >Thinking in terms of a list of files to be transferred, I would like: - >Anything present in common/ added to the file list; then - Anything >present in groupN/ added to the list, clobbering if applicable >(regardless of mtime) - The destination directory to show no sign of the >common / overlay structure The best solution will depend on the number of files in the special groups. Since you say the number is small, I suspect that something simple like: rsync -hia /path/to/sync/common remotehost: rsync -hia --ignore-times /path/to/sync/groupN remotehost: will be close to optimal. Another option is to build an --exclude-from list for the files in the special group and apply it to the first rsync. Then you can run the second rsync without the --ignore-times, which may result in faster overall throughput. FWIW, I think you will find the -hi output more useful than the -v output. Steven -- ------ "Steven Levine" <stev...@earthlink.net> Warp/DIY/BlueLion etc. www.scoug.com www.arcanoae.com www.warpcave.com -- -- 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: On the case `an identical item replaces the dots with spaces' for `--itemize-changes'.
In mgsrba$r6q$6...@ger.gmane.org, on 04/18/15 at 05:50 AM, Hongyi Zhao hongyi.z...@gmail.com said: Hi, are: (1) a newly created item replaces each letter with a +, (2) an identical item replaces the dots with spaces, and (3) an unknown attribute replaces each letter with a ? (this can hap pen when talking to an older rsync). But, I cann't figure out the case for the `(2) an identical item replaces the dots with spaces'. I'm pretty sure (2) only occurs when --itemize-changes is specified twice. This instructs rsync to list every item it examines even if it does not need to be updated. Steven -- -- Steven Levine stev...@earthlink.net Warp/DIY/eComStation etc. www.scoug.com -- -- 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: Rsync keeps copying everything to the server
In 206fad5f-53ea-49f1-abe8-411148b47...@gmail.com, on 10/01/14 at 07:14 PM, Juan Carlos Valle Sandoval jcvalle...@gmail.com said: Hi, rsync.exe -av --progress --log-file=/cygdrive/v/notes/archive/RSyncLogFile.txt /cygdrive/d/%username%/notes/archive /cygdrive/v/notes/ Since you running on Windows, you might have a timestamp resolution issue. The --itemize-changes recommended by others will show whether or not this is your issues. It's much more effective than -v in my experience. Steven -- -- Steven Levine stev...@earthlink.net Warp/DIY/eComStation etc. www.scoug.com -- -- 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: wildcards and nested files
In CAN0CFw1Q-z4oBLTuYfTS-a37ZzLb8=cwofnpfsgqxt7q1pn...@mail.gmail.com, on 07/03/13 at 02:55 AM, Grant emailgr...@gmail.com said: Hi Grant, Is there a rule I can apply to figure out the proper order for includes and excludes? Rules are evaluated in the order they are defined. The first rule with a pattern that that matches is the rule that applies. If you are a C programmer, think of it as the standard shortcut logical or (i.e. ||). Evaluation stops at the pattern that evaluates to true. If you really want to use rsync effectively, it will be worthwhile to fully understand the FILTER RULES and INCLUDE/EXCLUDE PATTERN RULES sections of the man page. The answers to your questions are there, but there's enough content that it can take a could of reads to get a feel for the developers way of thinking. Steven -- -- Steven Levine stev...@earthlink.net eCS/Warp/DIY etc. www.scoug.com www.ecomstation.com -- -- 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: wildcards and nested files
In can0cfw3jrk2saezrxxqfdz6lgnonwucpejfbr1pwv9mxujo...@mail.gmail.com, on 07/03/13 at 01:49 AM, Grant emailgr...@gmail.com said: Hi Grant, I couldn't agree more. May I suggest that the man page make reference to this feature under --include-from and --exclude-from ? It does, but you have to read the man page from top to bottom. As with all man pages, there's a trade off between repetition and useful cross-references. The man page states --exclude=PATTERN This option is a simplified form of the --filter option that defaults to an exclude rule and does not allow the full rule-parsing syntax of normal filter rules ... and --exclude-from=FILE This option is related to the --exclude option, but itspecifies a FILE that contains exclude patterns ... The include options are documented similarly. I also added a -i (--itemize-changes) because I am trying to generate a habit of always pairing it with -v since -v isn't all that useful FWIW, I always use -i and only use -v when debugging. Steven -- -- Steven Levine stev...@earthlink.net eCS/Warp/DIY etc. www.scoug.com www.ecomstation.com -- -- 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: wildcards and nested files
In can0cfw06x_7g-z3nthok35l2co4euv9h1+40yzpi_oi_8ff...@mail.gmail.com, on 07/02/13 at 12:25 PM, Grant emailgr...@gmail.com said: Hi, rsync -azvi --exclude-from=excludes.txt --delete --delete-excluded / user@hostname: excludes.txt: + / + /etc + /etc/** + /home + /home/*/ + /home/*/.maildir/ + /home/*/.maildir/** - - * So the includes are in excludes.txt prefixed with + and the excludes are prefixed with - - ? Since excludes.txt is an --exclude-from file, the - is optional. Similarly, if you are using an --include-from file, the + is optional. These are both specializations of the generic --filter='merge filters.txt' filter option. See the rsync man page for the gory details. Steven -- -- Steven Levine stev...@earthlink.net eCS/Warp/DIY etc. www.scoug.com www.ecomstation.com -- -- 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: rsync to sync time without attempting to modify the content
In 515b2c7f.8000...@gmail.com, on 04/02/13 at 12:07 PM, Brice Rebsamen brice.rebsa...@gmail.com said: Hi, options. But how to get rsync to give me info why files are different? Check the docs for --itemize-changes. This might be provide sufficient information to build your transfer lists. If not, take a look at the log format features in the rsync.conf docs. There's no way I can think of to have rsync update timestamps without first making the content equal, so this might be a separate script. Of course, you could always contract with someone familiar with the rsync code base to add a --assume-content-ok option. Steven -- -- Steven Levine stev...@earthlink.net eCS/Warp/DIY etc. www.scoug.com www.ecomstation.com -- -- 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: Maximum number of entries in a filter file
In 180601cda863$495c0b10$dc142130$@juno.co.uk, on 10/12/12 at 11:21 AM, Ben Yarwood ben.yarw...@juno.co.uk said: Hi, I have noticed that the .rsync-exclude file does not seem to be processed. I see no errors related to this in the output but believe it is because it contains over 120,000 entries and is maybe exceeding some internal 16bit limit in rsync of the number of entries that can be in a filter file. It's possible, but unlikely. On a 32-bit platform, integers are going to be 32-bit numbers and rsync uses these for the vast majority of the code. I would suspect the format of the exclude patterns. Perhaps they are not relative to the source path. If there is a limit other than available memory, it is unintentional. rsync version 3.0.6 protocol version 30 Copyright (C) 1996-2009 by Andrew Tridgell, Wayne Davison, and others. This build is a bit old, but I don't recall any issues with merge patterns. Regards, Steven -- -- Steven Levine stev...@earthlink.net eCS/Warp/DIY etc. www.scoug.com www.ecomstation.com -- -- 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: cannot rsync when source directory lacks write permission
In 64fab8215d47a944abdf7de50a3406a219c2dac...@esesscms0353.eemea.ericsson.se, on 08/10/12 at 09:27 AM, András Porjesz andras.porj...@ericsson.com said: Hi András, We may have to agree to disagree on some of this... Of course, the destination side must have enough rights to achieve what I need, and an rsyncd running as root:root surely have all the necessary rights. So using --perms with this daemon must have been sufficient. No, it's not the way it works and not the way I would want it to work. I do not want the server to automatically assume that the client can be trusted to do the right thing with data that is owned by the server. The fact that the rsync daemon is running as root is irrelevant. As you know from your many years of *ix experience, it is normal for a application running as root to use setuid to limit the rights it has. In my experience, it is typical for a server to do setuid nobody, unless instructed otherwise. But not, it is simply not true, because the daemon has a built-in assumption which overkills it. I know rsync sends its command line parameters to the daemon, so rsyncd could have been able to handle the case, but instead of recognizing the flag it simply makes that assumption. The assumption it makes is that the rsyncd.conf is correct when there is a choice to be made. This make absolutely good sense to me since in my world, the server knows what's best and the client is less trusted. 1. use exactly the same options on both sides This already happens. What does not happen is that the server does not automatically run as root. 2. specify which attributes to transfer (keep) and which ones to set explicitly (including permissions, ownership, time and probably acl also) This already happens. It is the client's responsibility to do this. The server will do it's best to fulfill the request. Failures can and will occur it the client asks the server to do something that exceeds its rights or is something the platform does not support. For example, I maintain an rsync port for a platform that does not support hard links. There's a whole set of client options that generate errors if the client requests them. 4. define a precedence (like: source filesystem, sender config, receiver config, receiver user rights, defaults) 5. describe actions taken in case of insufficient rights Most of this is already in place. If the server has insufficient rights the request will fail in some way and rsync will proceed, depending on options such as --ignore-errors. (just another example: client side -E, server side incoming chmod u+x,g-x and outgoing chmod u+x,g-x: what is the expected result when sending or receiving files?) As the man page says snip o To make a file executable, rsync turns on each x permission that has a corresponding r permission enabled. If --perms is enabled, this option is ignored. /snip Using aliases these can be mapped to the actual flags - for backward compatibility Huh? Steven -- -- Steven Levine stev...@earthlink.net eCS/Warp/DIY etc. www.scoug.com www.ecomstation.com -- -- 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: cannot rsync when source directory lacks write permission
In 64fab8215d47a944abdf7de50a3406a219c2dac...@esesscms0353.eemea.ericsson.se, on 08/09/12 at 07:54 AM, András Porjesz andras.porj...@ericsson.com said: Hi, Thanks, it looks ok, just it is not documented anywhere: From the ryncd.conf man page uidThis parameter specifies the user name or user ID that file transfers to and from that module should take place as when the daemon was run as root. In combination with the gid parameter this determines what file permissions are available. The default is uid -2, which is normally the user nobody. it overwrites the -perms flag on the other side. Not really. Se below. So read documentation, it is definitely against it: In summary: to give destination files (both old and new) the source permissions, use --perms. I assume you are referring to the rsync man page which says -p, --perms This option causes the receiving rsync to set the destination permissions to be the same as the source permissions. (See also the --chmod option for a way to modify what rsync considers to be the source permissions.) What it does not say is that the receiving side needs sufficient permissions to be able to change the permissions. I guess the man page authors assumed that someone running rsync on *ix would understand this implicitly. Running the receiving side as root is one option for ensuring that the receiver can change permissions. There are others that are more secure. Running the receiver as the default nobody user does not turn off --perms, it simply ensures that the attempt to change permissions is very likely to fail. One way to make it not fail is to have the module root owned by nobody. Regards, Steven -- -- Steven Levine stev...@earthlink.net eCS/Warp/DIY etc. www.scoug.com www.ecomstation.com -- -- 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: cannot rsync when source directory lacks write permission
In 64fab8215d47a944abdf7de50a3406a219c2cfb...@esesscms0353.eemea.ericsson.se, on 08/07/12 at 07:57 AM, András Porjesz andras.porj...@ericsson.com said: Hi, Probably it is related to this bug: https://bugzilla.samba.org/show_bug.cgi?id=8844 Well, this behavior is not a bug. It is the way rsync works. If a transfer runs as nobody, it's not going to be able to create much of anything on most setups. Running as nobody is typically used for anonymous rsync servers that need only read permission to the files in the module. Steven -- -- Steven Levine stev...@earthlink.net eCS/Warp/DIY etc. www.scoug.com www.ecomstation.com -- -- 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: cannot rsync when source directory lacks write permission
In CAFUyVX4O-o=r36MA0sMfhMMiPZSurLg3V0Z=qx_v1bz099g...@mail.gmail.com, on 08/07/12 at 01:03 PM, Greg Deback (rsync) greg.deb+rs...@gmail.com said: Hi, No I think this bug is not related. However, I am wondering : if the directory is write-protected, even for root, that means it never changes right ? No. As the code says /* We need to ensure that the dirs in the transfer have both * readable and writable permissions during the time we are * putting files within them. This is then restored to the * former permissions after the transfer is done. */ If András can not create files and/or dirctories at the destination, it is because the directory does not already have the required read/write permissions or the rsync daemon does not have the authority to change the permissions. Regards, Steven -- -- Steven Levine stev...@earthlink.net eCS/Warp/DIY etc. www.scoug.com www.ecomstation.com -- -- 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: cannot rsync when source directory lacks write permission
In juuivm$ai5$1...@dough.gmane.org, on 07/27/12 at 01:26 PM, Brian J. Murrell br...@interlinx.bc.ca said: Hi, I seem to be running into a problem where I am trying to rsync from a source directory that lacks write permissions (i.e. r-xr-xr-x). Presumably this is because rsync creates the directory on the destination, then sets the permissions to match the source and then tries to sync the contents of the directory, which it cannot of course lacking write permission in the directory. Rsync contains code to handle this. What version of rsync are you running and what is the command line you are using and what is the exact error message you are getting? Regards, Steven -- -- Steven Levine stev...@earthlink.net eCS/Warp/DIY etc. www.scoug.com www.ecomstation.com -- -- 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: Using rsync to synchronize
In 4f7caba1.3020...@sohnen-moe.com, on 04/04/12 at 01:14 PM, James Moe ji...@sohnen-moe.com said: Hi James, rsync --recursive --links --times --dirs --stats --delete \ --itemize-changes --quiet --exclude-from=exclude-filename \ /data-store1/ /data-store2/ FWIW, --dirs is rundundant in the above. Recently I have had the need to actually synchronize the files between two data stores. That is, whichever data store has the newest timestamp updates the other data store. Take a look at --existing and --update. Some combination of of these will probably get you the result you want. It depends on your definition of synchronize. Regards, Steven -- -- Steven Levine stev...@earthlink.net eCS/Warp/DIY etc. www.scoug.com www.ecomstation.com -- -- 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: Using rsync to synchronize
In 4f7cf7e1.5070...@sohnen-moe.com, on 04/04/12 at 06:39 PM, James Moe ji...@sohnen-moe.com said: Hi James, Please reply to the list so that others may participate. Neither, or both, of those options seem to meet my requirement. --existing, skip creating new files on receiver, appears to be counterproductive for synchronizing. As I said, it depends on how you define synchronize. There are times when I need to bring the existing files into sync while not adding any new files. This is where --existing is useful. The result is the files are synchronized, although the resulting file sets might not be identical. But I still see no way to update the sender's files if the receiver's files are newer. Would I have to run another rsync session with the sender and receiver reversed? Yes. I neglected to mention it because I considered it obvious. Sorry about that. Rsync is basically a very smart copy command. Rsync can be made act like a move command with the --remove-source-files, but this a special case. BTW, don't forget to drop the --delete from the command lines. Regards, Steven -- -- Steven Levine stev...@earthlink.net eCS/Warp/DIY etc. www.scoug.com www.ecomstation.com -- -- 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: cwRsync got killed...
In alpine.LNX.2.01.251354300.14380@hp.internal, on 11/25/11 at 02:29 PM, Benjamin R. Haskell rs...@benizi.com said: Hi, But they killed their sourceforge downloads, all, including past versions of cwrsync, including source. That seems pretty antisocial of them. Interesting. They are allowed to do what they want with the binaries, but the sources are another issue. As I read the GPL, they must continue to provide access to the sources for at least three years after the binary was last distributed. In addition, they must provide access to the actual sources used to build the binaries. For example, if itefix modified any of the rsync sources used to build the binaries, it's not sufficient to provide a link to the rsync sources at samba.org. http://sereds.git.sourceforge.net/git/gitweb.cgi?p=sereds/sereds;a=tree ... though I'm not sure it's what it says it is. To me, it looks the what they say it is, which is the install component of cwRsync. I don't know enough about Windows installers to say if it is complete. They can't prevent the source code from being distributed, if that's the case. Well, they are not really trying to do that. What they are doing is removing access at a site they control for the sources corresponding to binaries they distributed in the past. Perhaps, someone that is interested in cwRsync should contact itefix and ask them if there are any source code modifications. Another option is to contact the FSF and ask them to review the issue. This is after all, part of their charter. Regards, Steven -- -- Steven Levine stev...@earthlink.net eCS/Warp/DIY etc. www.scoug.com www.ecomstation.com -- -- 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: unpack_smb_acl() errors
In 20665313-68cb-416c-a4f9-02b6f5644...@comcast.net, on 10/23/11 at 11:16 AM, Robert DuToit rdut...@comcast.net said: I have been noticing this in stderr recently. Is this a problem? Standard OSX patches on 3.0.7 - everything working perfectly otherwise. Calling unpack_smb_acl() on /Users/astrid Offhand, I'd say this is leftover debug code. I don't see it in the unpatched sources. Take a look in acls.c for the message. Regards, Steven -- -- Steven Levine stev...@earthlink.net eCS/Warp/DIY etc. www.scoug.com www.ecomstation.com -- -- 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: Cannot get the syntax of --include-from right
In CAAykW6mMRiTVqt0KrrcgYiwNvz7kjHNQC76=rJc+c=+qpg3...@mail.gmail.com, on 09/16/11 at 07:34 PM, Robert Parker rlp1...@gmail.com said: HI Robert, nice -n 15 rsync -avl --exclude=.* \ --include-from=/home/bob/backup_includes \ $fromdir $todir Here is the content of /home/bob/backup_includes /home/bob/.vimrc /home/bob/.gitconfig The paths in your --include-from file must be relative to $fromdir. In general, this is true of all paths other than paths specified on the command line. The paths on the command line effectively create logic roots and the other paths will be relative to these paths. Steven -- -- Steven Levine stev...@earthlink.net eCS/Warp/DIY etc. www.scoug.com www.ecomstation.com -- -- 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: in/exclude[=] and multiple sources
In ce4bcf0b-f15a-4665-a5a7-de3c51183...@ukgb.net, on 08/19/11 at 11:49 AM, Ken Gillett email...@ukgb.net said: Hi Ken, I still think the docs should explain you can use either form. It does. The first paragraph of the OPTIONS section states snip rsync uses the GNU long options package. Many of the com- mand line options have two variants, one short and one long. These are shown below, separated by commas. Some options only have a long variant. The = for options that take a parameter is optional; whitespace can be used instead. /snip Are there ANY situations when either form will NOT work? Baring defects, no. So one can think of rsync working on each source in turn and applying all the include and exclude options to each source directory as it works on that source. That's what I already surmised so thanks for the confirmation. As stated in the second paragraph of the FILTER RULES section snip As the list of files/directories to transfer is built, rsync checks each name to be transferred against the list of include/exclude patterns in turn, and the first match- ing pattern is acted on: if it is an exclude pattern, then that file is skipped; if it is an include pattern then that filename is not skipped; if no matching pattern is found, then the filename is not skipped. /snip Mentally, I replace references to file and filename to file/directory, because that's really what is meant. The man page contains a lot of information, so it's easy enough to miss stuff even when one is looking for it specifically. Steven -- -- Steven Levine stev...@earthlink.net eCS/Warp/DIY etc. www.scoug.com www.ecomstation.com -- -- 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: FATAL I/O ERROR: dying...
In 4e27066a.4080...@sohnen-moe.com, on 07/20/11 at 09:46 AM, James Moe ji...@sohnen-moe.com said: The nightly rsync run is getting this error: 2011/07/20 02:04:29 [17840] FATAL I/O ERROR: dying to avoid a \ --delete-during issue with a pre-3.0.7 receiver The options are: - --archive --stats --compress --delete --itemize-changes What is needed to prevent the FATAL I/O ERROR? Add --delete-before or --delete-after. --delete defaults to --delete-during. Steven -- -- Steven Levine stev...@earthlink.net eCS/Warp/DIY etc. www.scoug.com www.ecomstation.com -- -- 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: Using rsync as an incremental backup
In 4e03c170.2020...@perturb.org, on 06/23/11 at 03:42 PM, Scott Baker sc...@perturb.org said: Hi, If it were local that would be easy. This is remote (via SSH), so I'd have to login before I run rsync to verify that directory is that. I was hoping I could save that step since rsync is already doing all that already. Your script should be able to use rsync to check if the link-dest directory exists with something like rsync --dirs bak...@perturb.org:/home/bakers/backup/$old/ However, I suspect that the multiple link-dest directories suggested by others will be a simplier solution. Steven -- -- Steven Levine stev...@earthlink.net eCS/Warp/DIY etc. www.scoug.com www.ecomstation.com -- -- 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: rsync and many files
In f992406d6e81b54dbb33210217fe7afd07f80...@exchange1.mtb.netclusive.de, on 06/06/11 at 12:04 PM, Cliff Simon cliff.si...@netclusive.com said: Hi, We are using rsync via rsnapshot, but this is not elementary. It is used to backup many (above 100 servers) and works very well. Now there is one server with many (several millions) files. The files are not very big, so the complete backup is about 500 GB. Now my problem is, that the backup needs about 14 hours - the most time is to generate the filelist and check whether the files are new/changed or not. My rsync-command is: /usr/bin/rsync -a --bwlimit=9000 --delete --numeric-ids --relative --delete-excluded --exclude=/some/pathes/ --rsh=/usr/bin/ssh --link-dest=/dest.path/daily.1/ root@192.x.x.x:/path.to.backup/ Do you have an idea to reduce the backup time? A bit of math says 2*10^6 / 14 hours is about 40 files/second. How fast do you think rsync should be and how does this compare to backups on your other servers? Are you sure the it is not the hardware that is limiting the rsync's performance? Based on my knowledge of the rsync sources, I believe the file list generation algorithms are pretty efficient. There is quite a bit of code in the code path, but it's hard to avoid this given the number of options available to control the sync process. Steven -- -- Steven Levine stev...@earthlink.net eCS/Warp/DIY etc. www.scoug.com www.ecomstation.com -- -- 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: Implicit --itemize
In 5.2.0.9.1.20110119091636.04a65ae0@localhost, on 01/19/11 at 09:17 AM, Fabian Cenedese cened...@indel.ch said: Hi, I use the same construct in other scripts without having this problem. So I think the escaping is already correct. The main reason might be the logfile command as Matt pointed out. I will try and see. My bad. Matt's answer is correct. I missed the --logfile reference. The quoting can be an issue on non-Linux platform, but it appears that you are running a Linux box. Steven -- -- Steven Levine stev...@earthlink.net eCS/Warp/DIY etc. www.scoug.com www.ecomstation.com -- -- 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: Very surprising behaviour with --files-from
In 20101210171139.gd27...@digitalkingdom.org, on 12/10/10 at 09:11 AM, Robin Lee Powell rlpow...@digitalkingdom.org said: Hi, $ rsync -i -aPv --ignore-existing --files-from=/tmp/list /backups/ ut00-s00010:/backups/ building file list ... 3937 files to consider That's not such a big deal, but the list I'm *actually* using has twenty *million* files in it. At a couple hundred files a second, if it's going to check 4 times the number of files, that's a *huge* time waste. What's going on? I'm not quite sure what's going on either. What I recommend is cut your list down to 1 file and use rsync -ii -aPv --ignore-existing --files-from=/tmp/list \ /backups/ ut00-s00010:/backups If this does not answer the question add one more -v. Steven -- -- Steven Levine stev...@earthlink.net eCS/Warp/DIY etc. www.scoug.com www.ecomstation.com -- -- 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: Very surprising behaviour with --files-from
In 20101210171139.gd27...@digitalkingdom.org, on 12/10/10 at 09:11 AM, Robin Lee Powell rlpow...@digitalkingdom.org said: Hi, After a quick testcase, I can see what's happenning. You have $ rsync -i -aPv --ignore-existing --files-from=/tmp/list /backups/ ut00-s00010:/backups/ building file list ... 3937 files to consider and cpool/b/c/5/bc5ea7a79a4824c6729645c66b562e6b Each subirectory counts as a file to consider. Steven -- -- Steven Levine stev...@earthlink.net eCS/Warp/DIY etc. www.scoug.com www.ecomstation.com -- -- 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 to sync an exact list of files, Including deletes!?
In aanlktindfc=z8o37ks9tcrleqpeumyd4753f_3mfb...@mail.gmail.com, on 11/20/10 at 10:56 PM, Axel Kittenberger axk...@gmail.com said: Hi, While running, Lsyncd knows exactly which files need transfer and rsync's --files-from (with =- to get the filelist from stdin-pipe) sounds like an ideal solution for this, also to reduce the number of times rsync gets spawned. Coded that, now in beta stage there is a nasty problem, rsync refuses to accept deletions that way! What might work for the deletes is a dynamically built --exclude-from list in combination with --delete excluded and possibly --prune-empty-dirs. I've never tried this with --files-from, but it should work as long as non-existant source file does not cause a problem with the filter logic. You should not need --recursive. You just need the --exclude-from file to contain full paths. Steven -- -- Steven Levine stev...@earthlink.net eCS/Warp/DIY etc. www.scoug.com www.ecomstation.com -- -- 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 to sync an exact list of files, Including deletes!?
In aanlktindfc=z8o37ks9tcrleqpeumyd4753f_3mfb...@mail.gmail.com, on 11/20/10 at 10:56 PM, Axel Kittenberger axk...@gmail.com said: Hi, While running, Lsyncd knows exactly which files need transfer and rsync's --files-from (with =- to get the filelist from stdin-pipe) sounds like an ideal solution for this, also to reduce the number of times rsync gets spawned. Coded that, now in beta stage there is a nasty problem, rsync refuses to accept deletions that way! My first idea did not work, which I thought might happen, but I came up with a reasonably cheap alternative using -dirs and filters. Try this command line rsync -n -i --dirs --delete-excluded -f._filters from/ to where filters contains + file1 + file2 R deleted P * The file list contains only file1 and file2 so the receiver has less work to do than without the filters. It should not be too difficult to expand this method to work for source files spread across multiple directories. One downside of this approach compared to --dirs without filters is that if something goes wrong at just the right time, the source and destination can get permamently out of sync. However, for directories with a large number of files, --dirs with filters should perform better. Perhaps the first update should use plain --dirs. Steven -- -- Steven Levine stev...@earthlink.net eCS/Warp/DIY etc. www.scoug.com www.ecomstation.com -- -- 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: rotating dirs created with link-dest
In alpine.bsf.2.00.1011160947100.50...@oceanpt.safeport.com, on 11/16/10 at 01:41 PM, d...@safeport.com said: H Doug, ---source-- base --dest-- rsync -e ssh r...@newharbor.safeport.com:/home --link-dest=/backup/201009/newharbor/home 201010/newharbor/ rsync -e ssh r...@newharbor.safeport.com:/home --link-dest=/backup/201003/newharbor/home 201010/newharbor/ The first command copies all files, the second command copied about 13 of 40 GB. The options on both commands are: -vaxH --numeric-ids --delete --exclude=/home/apache/logs The files are on backup box running some version of Linux. The command is running on FBSD 8.1 using rsync version 3.0.7 protocol version 30. Thanks for any help. Using -vvni I believe I can debug this. Probably. For my uses, -i is usually sufficient to dertermine why rync has decided to process a file/directory. Base on testing with my workstation perhaps using -c will do it. I don't think so. If I understand your issues, you are getting too many files copied on the second run. My first suspect would be user/group ids. Even if -c determines that the files contain the same content, the files still will get copied if the linking rules can not be satisfied. Steven -- -- Steven Levine stev...@earthlink.net eCS/Warp/DIY etc. www.scoug.com www.ecomstation.com -- -- 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: Multiple wildcards in source
In 201010292152.10643.alexc...@googlemail.com, on 10/29/10 at 09:52 PM, Alex Cartwright alexc...@googlemail.com said: Unfortunately I have tried it without the quotes as well, with no luck. $ sudo rsync -arv /home/*/domains/* /home/alex/foo/ [sudo] password for alex: sending incremental file list rsync: change_dir /home/*/domains failed: No such file or directory (2) There's something odd going on with your shell or your wildcard needs to be tweaked. What does ls /home/*/domains/* have to say? Regards, Steven -- -- Steven Levine stev...@earthlink.net eCS/Warp/DIY etc. www.scoug.com www.ecomstation.com -- -- 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: include-from or files-from
In aanlkti=z1bpcuh-bhfqc0e7cudin2pkghxdav9jqs...@mail.gmail.com, on 10/25/10 at 10:18 AM, ml ml mliebher...@googlemail.com said: Hi, Please reply to the list. ma...@mario-laptop:~/foo2$ find . . ./include.txt ./file-also-included ./path ./path/this-file-is-found ./some My rsync command: rsync -avnz --recursive --include-from=include.txt * bar FWIW, -a implies --recursive. FWIW, there's no real benefit to -z for local transfers. Less data goes through the pipes, but the compression logic takes CPU cycles. As a matter of style, I would use --filter=include.txt, since what you have is a filter list rather than a simple include list. cat include.txt + /some/ + /some/path/ + /some/path/this-file-is-found + /file-also-included - * rsync -avnz --recursive --include-from=include.txt * bar sending incremental file list created directory bar file-also-included some/ sent 89 bytes received 19 bytes 216.00 bytes/sec total size is 0 speedup is 0.00 (DRY RUN) Why does it not transfer the files recursively? It does, but you told rsync to ignore all the other directories with -*. This is a downside of using the paridigm. Depending on your needs, --prune-empty-dirs may be a better solution. Also, to be consistent with your find finds, you command line needs to be rsync -n -ai --filter=include.txt ./ bar Steven -- -- Steven Levine stev...@earthlink.net eCS/Warp/DIY etc. www.scoug.com www.ecomstation.com -- -- 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: rsync: failed to set permissions on filename: Function not implemented (38)
In 4cc6309c.4080...@enabled.com, on 10/25/10 at 06:36 PM, Noah noah-l...@enabled.com said: Hi, rsync: failed to set permissions on filename: Function not implemented (38) and the command line is /usr/bin/rsync --recursive --compress --human-readable --progress --update --perms -avz '/Applications' -e 'ssh -p 22 -o ServerAliveInterval=10' --relative --delete root@hostname:/directory What can I do to alleviate these errors? I recommend you start with providing sufficient information, so that someone might be responds with more than general comments. Obviously, you need to indicate the client and host platforms and the rsync versions these platforms are running. Offhand it appears that the server does not support a mode change requested by the client. Adding --itemize-changes might help you identify if the error is specific to a particular file. Steven -- -- Steven Levine stev...@earthlink.net eCS/Warp/DIY etc. www.scoug.com www.ecomstation.com -- -- 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 to escape () characters in commad
In 1287873889527-3008848.p...@n4.nabble.com, on 10/23/10 at 03:44 PM, rlinsurf rlins...@dhnet.us said: Hi, /usr/local/bin/rsync -avv 'Jeffrey s iPhone (Root)'/ 'Macintosh HD'/Users/jeffrey/Downloads/iphone_backup When there are spaces in the file name, it is typical to need to supply --protect-args. Steven -- -- Steven Levine stev...@earthlink.net eCS/Warp/DIY etc. www.scoug.com www.ecomstation.com -- -- 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: include-from or files-from
In aanlktim93g-cp9obghze3jx8jrnwelyjoe=whthr5...@mail.gmail.com, on 10/22/10 at 11:30 AM, ml ml mliebher...@googlemail.com said: Hi listee, If i change my file list to: ...snip... + 165/165950* + 166/166072* - * ...snap... This is a common use case. Read the man page section titled INCLUDE/EXCLUDE PATTERN RULES and find the part that reads + /some/ + /some/path/ + /some/path/this-file-is-found + /file-also-included - * It should help you understand how to set up the filter rules you need. The docs discuss a couple of other ways to solve this problem. Regards, Steven -- -- Steven Levine stev...@earthlink.net eCS/Warp/DIY etc. www.scoug.com www.ecomstation.com -- -- 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: rotating dirs created with link-dest
In alpine.bsf.2.00.1010181323010.40...@oceanpt.safeport.com, on 10/18/10 at 01:41 PM, d...@safeport.com said: Hi Doug, If I change link-dest=../../201009/myserver/home/ it starts a new base. Via google and RTFM it seems that naming schemes keep the name of the link-dest directory constant. Is this a requirement or am I yet missing one more thing? I suspect the option name is confusing you. --link-dest names the source of the basis files so you don't want it to be empty (or new). You need to reverse the options as in rsync srcdir --link-dest=last-backup-dir new-backupdir Steven -- -- Steven Levine stev...@earthlink.net eCS/Warp/DIY etc. www.scoug.com www.ecomstation.com -- -- 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: Excluding most and including some problems continue.
In 4ca449ea.2858.00a...@cdpr.ca.gov, on 09/30/10 at 08:27 AM, Ian Skinner iskin...@cdpr.ca.gov said: Hi, Here is my rsync command as it currently stands. /usr/local/bin/rsync -vvv --stats -Pzrtpl --delete --password-file=/export/home/webuser/.appprod --log-file=/export/home/webuser/logs/rsync-log -F /export/home/ webu...@appprod::dprweb_extranet/ rsync-test This is doing pretty close to what I want it to do. Which is to mirror only the */htdocs/docs* in each of the ten directories (das,em,enf,etc.) in the base path of */export/home* and exclude the rest. I'm not sure I entirely understand what you want, but what about + das/**/htdocs/docs* + em/**/htdocs/docs* etc. or possibly + das/**htdocs/docs* + em/**/htdocs/docs* etc. I'm not sure if the addtional slash is required without setting up a testcase. If you really want just the files matching */htdocs/docs/*, the above needs to change slightly. Steven -- -- Steven Levine stev...@earthlink.net eCS/Warp/DIY etc. www.scoug.com www.ecomstation.com -- -- 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: Excluding most and including some problems continue.
In 4ca4958c.2858.00a...@cdpr.ca.gov, on 09/30/10 at 01:50 PM, Ian Skinner iskin...@cdpr.ca.gov said: Hi, or possibly + das/**htdocs/docs* + em/**/htdocs/docs* etc. I'm not sure what the difference between the first example and the second example is supposed to be? That's my bad eyes. This should have been + das/**htdocs/docs* + em/**htdocs/docs* but it's not going to do what you really want. I don't see how that would address my needs, but I'm not sure what the double ** symbols represent? I recommend you read the man page. ** and *** can be very useful. But there is no extra directories between the das and the htdocs directories in my use case. OK. That's why I said I was not sure what you were asking. I want to mirror the following directories from the above example and exclude everything else. /export/home/em/htdocs/docs/* /export/home/enf/htdocs/docs/* /export/home/das/htdocs/docs/* (And seven more similar directories) OK. This is easier. I just tried this filter file somewhat based on your previous suggestion but it excluded everything. It's close, but you need to augment is a bit. Try + das/htdocs/docs/* + em/htdocs/docs/* etc. + */ - * and add --prune-empty-dirs to the command line. Also, if you really only want the contents of specific directories and not the content of any of the subdirecories, you can often avoid the recursive scan and use the --relative option and just list the source directories on the command line. Steven -- -- Steven Levine stev...@earthlink.net eCS/Warp/DIY etc. www.scoug.com www.ecomstation.com -- -- 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: Excluding most and including some problems continue.
In 4ca4be08.2858.00a...@cdpr.ca.gov, on 09/30/10 at 04:42 PM, Ian Skinner iskin...@cdpr.ca.gov said: Hi, + das/htdocs/docs/* + em/htdocs/docs/* etc. + */ - * Thanks for the suggestion, but that did not seem to produce the desired results. I did not look into why in detail, but a dry run produced files from directories I wanted to exclude and apparently not all the files I wanted to include. Did you add --prune-empty-directorys to the command line? This filter setup along with --prune-empty-directories will copy only the files in the named directores, which is my understanding of what you want. After a day of trail and error and internet searching I now have this that is really close. Looks overly complex to me. Taking your example layout and using this filter set + das/htdocs/docs/* + em/htdocs/docs/* + enf/htdocs/docs/* + internal/htdocs/docs/* + itb/htdocs/docs/* + medtox/htdocs/docs/* + pml/htdocs/docs/* + psb/htdocs/docs/* + reg/htdocs/docs/* + whs/htdocs/docs/* + */ - * and this command line rsync --dry-run --prune-empty-dirs --itemize-changes -a -F export\ to\ I get .d..t.. ./ cd+ home/ cd+ home/das/ cd+ home/das/htdocs/ cd+ home/das/htdocs/docs/ f+ home/das/htdocs/docs/SHLNotes.txt cd+ home/em/ cd+ home/em/htdocs/ cd+ home/em/htdocs/docs/ f+ home/em/htdocs/docs/SHLNotes.txt Which I think is what you want. Every subdirectory contains a file. Good luck, Steven -- -- Steven Levine stev...@earthlink.net eCS/Warp/DIY etc. www.scoug.com www.ecomstation.com -- -- 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: is a - *.ext filter overriden by a later + *.ext
In 20100909135257.ga20...@apartia.fr, on 09/09/10 at 03:52 PM, Louis-David Mitterrand vindex+lists-rs...@apartia.org said: Hi, Are such entries supposed to cancel each other? How can one override an earlier exclude in a filter list? You need to prepend the overrides to your list rather than appending them. In general, rules are processed top down and the first rule that applies stops subsequent rules from being evaluated. I recommend you review the FILTER RULES section of the man page. It says snip As the list of files/directories to transfer is built, rsync checks each name to be transferred against the list of include/exclude patterns in turn, and the first match- ing pattern is acted on: if it is an exclude pattern, then that file is skipped; if it is an include pattern then that filename is not skipped; if no matching pattern is found, then the filename is not skipped. /snip Steven -- -- Steven Levine stev...@earthlink.net eCS/Warp/DIY etc. www.scoug.com www.ecomstation.com -- -- 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: Does rsync use encription also for local tranfers?
In 20100816120251.117...@gmx.com, on 08/16/10 at 12:40 PM, forli...@gmx.com said: Hi, Does rsync use encription also for local tranfers? No. In addition, rsync defaults to --whole-file; that is it delta-xfer is disabled. The effective speed per file should be similar to cp or copy, depending on your OS. I'm asking because the speed of local transfers doesn't seem quite good for an USB 2.0 connected hard drive. What is the speed according to --stats? Steven -- -- Steven Levine stev...@earthlink.net eCS/Warp/DIY etc. www.scoug.com www.ecomstation.com -- -- 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: the meaning of receiving file list
In 201005011849.17023.michael.ren...@gmx.de, on 05/01/10 at 06:49 PM, Michael Renner michael.ren...@gmx.de said: Hi, where can I find an explanation for all these codes in the verbose output: cd..t.. root/ f..t.. root/.Xauthority f.st.. root/Dokumente und Einstellungen/test2.txt f+ test.txt cd+ global/foo This is the output of --itemize-changes. See http://samba.org/ftp/rsync/rsync.html. Regards, Steven -- -- Steven Levine stev...@earthlink.net eCS/Warp/DIY etc. www.scoug.com www.ecomstation.com -- -- 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: log information .d..t... etc
In loom.20090802t094306-...@post.gmane.org, on 08/02/09 at 09:46 AM, Dean Rotherham d...@skynetwork.co.za said: Hi, 2009/08/02 11:38:58 [5596] .d..t.. music00/ 2009/08/02 11:39:01 [5595] sent 40 bytes received 53 bytes total size 9603099 2009/08/02 11:39:05 [5597] receiving file list 2009/08/02 11:39:07 [5598] .d..t.. music01/ What does the .d..t. line mean? This is described in the section that dicusses the --itemize-changes option. Agian I hope I'm not asking a FAQ question here but I can't seem to find reference to what these log switches relate to. It's a bit indirect. When you request a log, --itemize-changes is implied. Hope to chat soon. Regards, Steven -- -- Steven Levine stev...@earthlink.net eCS/Warp/DIY etc. www.scoug.com www.ecomstation.com -- -- 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: Rsnapshot/rsync buffer overflow
In c685735d.32a1%kurtisnel...@gmail.com, on 07/17/09 at 12:16 AM, Kurtis Nelson kurtisnel...@gmail.com said: Hi, I have been using rsnapshot on OS X for a bit now to backup my debian home server to my external HD but have now started getting this error. ERROR: buffer overflow in recv_file_entry [generator] rsync error: error allocating core memory buffers (code 22) at util.c(124) [generator=3.0.6] A stock rsync build has a hardcoded 1024 character limit on pathnames. The actual limit ca be slightly less. It appears you have exceeded this limit. Regards, Steven -- -- Steven Levine stev...@earthlink.net eCS/Warp/DIY etc. www.scoug.com www.ecomstation.com -- -- 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: Rsnapshot/rsync buffer overflow
In c1e87fb7-a3b8-4aa9-93f8-bff0effd9...@gmail.com, on 07/17/09 at 01:46 PM, Kurt Nelson kurtisnel...@gmail.com said: Hi Kurt, Please reply to the list... Any good workarounds? Depends on your needs. If you really need names this long, rsync builds pretty easily. Change the pathname max to something you can live with rsync should stop complaining. Look for MAXPATHLEN. Regards, Steven -- -- Steven Levine stev...@earthlink.net eCS/Warp/DIY etc. www.scoug.com www.ecomstation.com -- -- 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
