RE: [Question] Building without iconv

On March 3, 2025 10:28 PM, Kevin Korb wrote: >Works for me... >$ ./configure --disable-iconv --disable-locale --disable-openssl >--disable-xxhash -- >disable-zstd --disable-lz4 && make $ ldd rsync > linux-vdso.so.1 (0x7ffd39873000) > libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6

Re: [Question] Building without iconv

Works for me... $ ./configure --disable-iconv --disable-locale --disable-openssl --disable-xxhash --disable-zstd --disable-lz4 && make $ ldd rsync linux-vdso.so.1 (0x7ffd39873000) libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7f77c8f8b000) /lib64/ld-linux-x86-64

RE: [Question] Building without iconv

On March 3, 2025 9:14 PM Marc Aurèle La France wrote: >On Mon, 2025-Mar-03, Randall S. Becker via rsync wrote: > >> I am trying to build a 64-bit version of rsync. My issue is that I do >> not have a 64-bit libiconv.so or libiconv.a available. The platform I >> am on only has 32-bit builds. The --d

Re: [Question] Building without iconv

On Mon, 2025-Mar-03, Randall S. Becker via rsync wrote: I am trying to build a 64-bit version of rsync. My issue is that I do not have a 64-bit libiconv.so or libiconv.a available. The platform I am on only has 32-bit builds. The --disable-iconv option in configure is not actually disabling icon

[Question] Building without iconv

Hi Rsync Team, I am trying to build a 64-bit version of rsync. My issue is that I do not have a 64-bit libiconv.so or libiconv.a available. The platform I am on only has 32-bit builds. The --disable-iconv option in configure is not actually disabling iconv. Is there a different option to disable t

Re: question about the recursive algorithm

> I don't believe the transferring part of rsync will jump around. How about the deleting part? > It will transfer files it deems need it in the order it finds them > which will be 1 dir at a time. Though when it enters a child dir that > doesn't mean it is done with the parent dir. In the sen

Re: question about the recursive algorithm

parent dir. On Thu, 16 Jan 2025, b...@riseup.net wrote: Date: Thu, 16 Jan 2025 15:16:02 + From: b...@riseup.net To: Kevin Korb Cc: rsync@lists.samba.org Subject: Re: question about the recursive algorithm Thanks for your message again. I appreciate your answers. I don't mind about t

Re: question about the recursive algorithm

Thanks for your message again. I appreciate your answers. I don't mind about the order of the files, and neither really about the order of the directories: I'm interested about whether rsync might transfer some files into a directory, then transfer some files into another which is outside of the f

Re: question about the recursive algorithm

it is quite common for it to delete things in directories it isn't transferring files in. On Thu, 16 Jan 2025, BP25 wrote: Date: Thu, 16 Jan 2025 14:47:27 + From: BP25 To: Kevin Korb Cc: rsync@lists.samba.org Subject: Re: question about the recursive algorithm Thanks Kevin, but I

Re: question about the recursive algorithm

Thanks Kevin, but I don't understand your message, or at least how it answers my "real question" (last paragraph)... and by the way --delete defaults to --delete-during for current versions of rsync as far as I know... > rsync doesn't really give much control over the or

Re: question about the recursive algorithm

P via rsync wrote: Date: Thu, 16 Jan 2025 13:53:04 + From: BP via rsync To: rsync@lists.samba.org Subject: question about the recursive algorithm Hello, I always run rsync as follows: "sudo rsync -PaSHAXvi --del DIR1/ DIR2". I would think that whenever I see in the output of this

Re: question about the recursive algorithm

rs. But here's the real question: is my hypothesis correct when we restrict to just lines starting by >, and also to just lines which start by *deleting? In other words, does the sender never jump folder and back, and same the receiver (but combined they might, as shown above)? I would

question about the recursive algorithm

df *deleting A/C/file5.txt cd+ A/B/folder2/ >f+ A/B/folder2/file6.html Is this expected? Reading the manual (section about inductive recursion) I would think that the only case where rsync jumps unfinished dirs would be the creation of empty dirs. But here's the real qu

Re: question about --link-dest and the rsync protocol

Thanks for the advice. Unfortunately I tried: --link-dest=/snapshots/rsync_test/last and it still does not find it. On Sun, Jan 12, 2025 at 8:37 AM Paul Slootman via rsync wrote: > > On Sat 11 Jan 2025, Anthony LaTorre via rsync wrote: > > > Thanks for your quick response. The rsyncd.conf file

Re: question about --link-dest and the rsync protocol

On Sat 11 Jan 2025, Anthony LaTorre via rsync wrote: > Thanks for your quick response. The rsyncd.conf file looks like: > > charset = utf-8 > [user] > path = /c/user > comment = "" > use chroot = true Note the chroot... So "/" equals /c/user > uid = root > gid = root > read only = f

Re: question about --link-dest and the rsync protocol

On 12.01.25 03:52, Anthony LaTorre via rsync wrote: $ rsync -aPh --link-dest=/user/snapshots/rsync_test/last /home/user/rsync_test rsync://admin@readynas.internal/snapshots/user/Jan_11_2025 Password: sending incremental file list --link-dest arg does not exist: /user/snapshots/rsync_test/last

Re: question about --link-dest and the rsync protocol

Hi Kevin, Thanks for your quick response. The rsyncd.conf file looks like: charset = utf-8 [user] path = /c/user comment = "" use chroot = true uid = root gid = root read only = false auth users = admin I'm still confused about how to specify the path. The actual UNIX path is: /c/

Re: question about --link-dest and the rsync protocol

rsyncd doesn't take unix paths. You must adapt your --link-dest to contend with however the rsycd module is defined in rsyncd.conf. On 1/11/25 9:52 PM, Anthony LaTorre via rsync wrote: Hi all, I'm trying to figure out why a script works when using SSH but not when using the rsync protocol. Wh

question about --link-dest and the rsync protocol

Hi all, I'm trying to figure out why a script works when using SSH but not when using the rsync protocol. When I run the following command: rsync -aPh --link-dest=/user/snapshots/rsync_test/last /home/user/rsync_test root@readynas.internal:/user/snapshots/rsync_test/Jan_11_2025 it works perfectl

Re: Question About Rsync and Modification Times

On Wed 09 Oct 2024, McDowell, Blake via rsync wrote: > Linux servers one running TrueNAS-13.0-U6 and the other running > TrueNAS-13.0-U3.1. > > I connect to both on a Mac via smb over fiber. > > Using cp -a also updates the timestamp of the copied file to today and does > not back-date it to t

Re: Question About Rsync and Modification Times

conservator/archivist, so I may be missing something obvious. -Blake From: Kevin Korb Date: Wednesday, October 9, 2024 at 15:01 To: McDowell, Blake , rsync@lists.samba.org Subject: Re: Question About Rsync and Modification Times External Email - Exercise Caution That isn't how rsync s

Re: Question About Rsync and Modification Times

a.org *Subject: *Re: Question About Rsync and Modification Times External Email - Exercise Caution You are using rsync -a which copies (preserves) the timestamp.  Meaning that rsync will copy the file then back-date it to the timestamp of the source file.  Most copying tools do not do this though cp

Re: Question About Rsync and Modification Times

Date: Wednesday, October 9, 2024 at 14:45 To: rsync@lists.samba.org Subject: Re: Question About Rsync and Modification Times External Email - Exercise Caution You are using rsync -a which copies (preserves) the timestamp. Meaning that rsync will copy the file then back-date it to the timestamp

Re: Question About Rsync and Modification Times

estamp wouldn't be different and rsync would have just skipped it. On 10/9/24 14:06, McDowell, Blake via rsync wrote: Hello, I have a question about how/why rsync updates modification times, which I haven’t been able to find an answer to. I have two locally connected storage devices runn

Question About Rsync and Modification Times

Hello, I have a question about how/why rsync updates modification times, which I haven’t been able to find an answer to. I have two locally connected storage devices running TrueNAS Core: one is new and empty, while the other is filled with files. When I run the following rsync command

Question: Is CAREFUL_ALIGNMENT=1 needed for rsync on RISC-V

r +3);     printf("x2=%x\n",x);     printf("out[0]=%x, out[1]=%x\n",out[0],out[1]);     return 0; } ``` So, my question is, is CAREFUL_ALIGNMENT=1 necessary for RISC-V? Although misalignment accesses will suffer from a large time penalty on RISC-V, I guess it can still run fa

Re: A question about rsync filters, not sure if I understand the man page

On Tue, Jul 16, 2024 at 05:56:28PM +0200, francis.montag...@inria.fr wrote: > Hi. > > On Tue, 16 Jul 2024 16:00:47 +0100 Chris Green via rsync wrote: > > > I run a daily backup using 'rsync -a -F ' > > > I want to exclude everything in ~/.local/share **except** the file:- > > >/home/chr

Re: A question about rsync filters, not sure if I understand the man page

On Tue, 16 Jul 2024 11:12:54 -0700 Ian Z via rsync wrote: > On Tue, Jul 16, 2024 at 05:56:28PM GMT, Francis.Montagnac--- via rsync wrote: >> No. Assuming you are doing this backup from your homedir, you should >> add to your .rsync-filter file: >> + /.local/ >> + /.local/share/ >> + /.loca

Re: A question about rsync filters, not sure if I understand the man page

On Tue, Jul 16, 2024 at 05:56:28PM GMT, Francis.Montagnac--- via rsync wrote: > > I want to exclude everything in ~/.local/share **except** the file:- > >/home/chris/.local/share/evolution/calendar/system/calendar.ics > > I have the following in my rsync-filter file to exclude ~/.local/share

Re: A question about rsync filters, not sure if I understand the man page

Hi. On Tue, 16 Jul 2024 16:00:47 +0100 Chris Green via rsync wrote: > I run a daily backup using 'rsync -a -F ' > I want to exclude everything in ~/.local/share **except** the file:- >/home/chris/.local/share/evolution/calendar/system/calendar.ics > I have the following in my rsync-fil

A question about rsync filters, not sure if I understand the man page

I run a daily backup using 'rsync -a -F ' I want to exclude everything in ~/.local/share **except** the file:- /home/chris/.local/share/evolution/calendar/system/calendar.ics I have the following in my rsync-filter file to exclude ~/.local/share - .local/share Can I simply add the fol

Re: question abount pre-xfer exec

You only log you would like to to mount /backup, but the actual command is missing. You should also log errors, so something like /usr/bin/mount /backup >> /var/log/rsyncd.log 2>&1 would be adequate before your line to check what is mounted. Hope this helps Hardy Am 24.09.22 um 15:15 schrob d

Re: question abount pre-xfer exec

You aren't logging any stderr. That is where any error messages would go. Add some 2>&1. Also, mount has a -v On 9/24/22 09:15, dotdeb--- via rsync wrote: I've been using rsync for years to backup my machines both at work and at home. These days I faced a new "challenge": at work I connect

question abount pre-xfer exec

I've been using rsync for years to backup my machines both at work and at home. These days I faced a new "challenge": at work I connect my laptop to a docking station with an external usb disk. I'd like to use this disk as a backup volume. I put my disk in /etc/fstab to be mounted at boot (with 'n

Re: quick question: --rsh="ssh -l root"

No. On Sun, Aug 07, 2022 at 06:49:45AM +0200, Fourhundred Thecat via rsync wrote: > Hello, > > is there any difference/advantage between these two commands? > > rsync --rsh="ssh -l root" my-host.com > rsync r...@my-host.com > > thank you, > > -- > Please use reply

quick question: --rsh="ssh -l root"

Hello, is there any difference/advantage between these two commands? rsync --rsh="ssh -l root" my-host.com rsync r...@my-host.com thank you, -- Please use reply-all for most replies to avoid omitting the mailing list. To unsubscribe or change options: https://lists

Re: Question about rsync -uav dir1/. dir2/.: possib to link?

Yes, cpio -l can be useful since cpio can easily operate on the output from the very capable find command. On 9/4/21 8:34 PM, Dan Stromberg wrote: > > I was thinking --link-dest too. > > Sometimes this can be done with cpio too; check out the -pdlv options. > > On Sat, Sep 4, 2021 at 4:57 PM Ke

Re: Question about rsync -uav dir1/. dir2/.: possib to link?

I was thinking --link-dest too. Sometimes this can be done with cpio too; check out the -pdlv options. On Sat, Sep 4, 2021 at 4:57 PM Kevin Korb via rsync wrote: > Rsync does almost everything cp does but since it is designed to network > it never got that feature. I was thinking maybe --link-

Re: Question about rsync -uav dir1/. dir2/.: possib to link?

Rsync does almost everything cp does but since it is designed to network it never got that feature. I was thinking maybe --link-dest could be tortured into doing it but if it can I can't figure out how. BTW, you have some pointless dots in there. On 9/4/21 6:41 PM, L A Walsh via rsync wrote: > I

Question about rsync -uav dir1/. dir2/.: possib to link?

I noticed in looking at download dirs for a project, that another mirror had "crept-in" for usage (where different mirrors are stored under mirror-URL names). To copy over the diffs, normally I'd do: rsync -uav dir1/. dir2/. (where dir1="the new mirror that I'd switched to by accident, and dir2=

Re: Syntax Question on 'rsyncd.conf' on Windows

On 4/9/21 5:05 PM, Dan Stromberg wrote: This is probably more of a Cygwin question than an rsync question. On Cygwin, E: should show up automatically as /cygdrive/e You can test that by opening a Cygwin terminal and cd'ing to /cygdrive/e Thanks! -- Please use reply-all for most repli

Re: Syntax Question on 'rsyncd.conf' on Windows

This is probably more of a Cygwin question than an rsync question. On Cygwin, E: should show up automatically as /cygdrive/e You can test that by opening a Cygwin terminal and cd'ing to /cygdrive/e On Tue, Apr 6, 2021 at 1:32 PM Tim Evans via rsync wrote: > Cygwin distribution of r

Syntax Question on 'rsyncd.conf' on Windows

Cygwin distribution of rsync for Windows contains an example rsyncd.conf, excerpt below: [cDrive] path = /cygdrive/c/ comment = Entire C Drive Having trouble setting up a second Windows physical drive. Is the "cygdrive" designation a reference to the full system root, so that syntax for

Re: Question/comment about -n (dry run) flag of rsync

No problem On Tue, Mar 10, 2020, 18:05 raf via rsync wrote: > raf via rsync wrote: > > > T. Shandelman via rsync wrote: > > > > > Rsync is a remarkably handy tool that I use virtually every day. > > > > > > But there is one thing about rsync that drives me totally crazy. > > > > > > Under the -n

Re: Question/comment about -n (dry run) flag of rsync

raf via rsync wrote: > T. Shandelman via rsync wrote: > > > Rsync is a remarkably handy tool that I use virtually every day. > > > > But there is one thing about rsync that drives me totally crazy. > > > > Under the -n (dry run) flag, rsync seems to produce exactly the same output > > as withou

Re: Question/comment about -n (dry run) flag of rsync

T. Shandelman via rsync wrote: > Rsync is a remarkably handy tool that I use virtually every day. > > But there is one thing about rsync that drives me totally crazy. > > Under the -n (dry run) flag, rsync seems to produce exactly the same output > as without that flag. > > I cannot tell you ho

Re: Question/comment about -n (dry run) flag of rsync

PGP public key available on web site. ~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._., On Tue, 10 Mar 2020, T. Shandelman via rsync wrote: Date: Tue, 10 Mar 2020 17:26:41 -0500 From: T. Shandelman via rsync To: rsync@lists.samba.org Subject: Question/comment about -n (dry run

Question/comment about -n (dry run) flag of rsync

Rsync is a remarkably handy tool that I use virtually every day. But there is one thing about rsync that drives me totally crazy. Under the -n (dry run) flag, rsync seems to produce exactly the same output as without that flag. I cannot tell you how many times I sit and scratch my head long and

question about batches

Hi, I'm using "only-write-batch" and "read-batch" to syncronize a debian root filesystem with some personalized software on it, from a central server to remote devices (all with RO filesystem, and perfectly identical among them). In this way I'm able to push from my master device to an "updater"

Rrsync3.1.3x POSIX ACLs conversion to NFS v4 ACLs question

OSIX ACLs applied on some files, the reason we are using "-XA" is because we also have NFS v4 ACLs to copy and this works. Our problem or question is about POSIX ACL, when we mount source as NFS v4 and destination as NFS v4, it seems like all the POSIX ACLs being converted into NFS v4

Re: Kudos and feature question

Thank you for the thorough answer, very helpful. I’ll start poking around! best regards, Francois > On Mar 24, 2019, at 6:27 PM, Dave Gordon wrote: > > I think you would implement it as a new type of filter rule. similar to 'P' > (preserve) but with a timestamp or delta-time to define what co

Re: Kudos and feature question

I think you would implement it as a new type of filter rule. similar to 'P' (preserve) but with a timestamp or delta-time to define what counts as 'recent' as well as the pattern to match for this rule to apply (which could just be a wildcard matching anything by default, but could also use the

Kudos and feature question

Kudos all that maintain this awesome and enduring piece of software. Awesome job, many thanks. I’ve come across a use case that would greatly benefit form a —delete-older-than argument. This would behave the same as —delete only sparing files dest that have a creating time less than ago. How

Question about patch-hfs-compression.diff and rsync 3.1.3

Hi, Is there any information anywhere about what specifically is broken with rsync 3.1.3 and the patch patch-hfs-compression.diff ? Both MacPorts and Homebrew's package build files exclude patch-hfs-compression.diff for rsync 3.1.3, saying "hfs-compression.diff is marked by upstream as broken as

Re: Yet another filter question

If a directory is empty (after filtering) then --prune-empty-dirs prunes it. That is the point. The option exists to keep rsync from copying directories when all of the contents of the directory have been filtered out. On 10/25/2017 10:09 PM, dave_g via rsync wrote: > Given the structure… > /foo

Yet another filter question

Given the structure… /foo/bar/want-this.txt /foo/bar/want-this-2.txt /bar/foo/ /do-not-want-to-transfer/test.txt With the desire to ‘include items with foo in their path’... I understand that the closest I can get to a satisfactory filter ruleset is something like: + **foo** + */ - * … and setting

Re: Yet another filter question

Wayne Davison wrote... > On Tue, May 3, 2016 at 1:07 PM, Christoph Biedl wrote: > > > + *.git/.git/* > > - *.git/ > > > > >From the man page near the start of the "INCLUDE/EXCLUDE PATTERN RULES" > section: > > *Note that, when using the --recursive (-r) option (which is implied by > > -a),

Re: Yet another filter question

On Wed, 4 May 2016 21:26:26 -0500 "Karl O. Pinc" wrote: > On Wed, 4 May 2016 21:09:44 -0400 > Kevin Korb wrote: > > > That wording from the man page makes almost no sense without the > > examples directly after it (and I have read it many times and know > > what it is saying). > Patch append

Re: Yet another filter question

On Wed, 4 May 2016 21:09:44 -0400 Kevin Korb wrote: > That wording from the man page makes almost no sense without the > examples directly after it (and I have read it many times and know > what it is saying). Makes sense to me. The only thing I'd change is to use "in a depth first fasion" inst

Re: Yet another filter question

On Wed, 4 May 2016 21:09:44 -0400 Kevin Korb wrote: > That wording from the man page makes almost no sense without the > examples directly after it (and I have read it many times and know > what it is saying). Makes sense to me. The only thing I'd change is to use "in a depth first fasion" inst

Re: Yet another filter question

I hate to say anything remotely negative to Wayne but... That wording from the man page makes almost no sense without the examples directly after it (and I have read it many times and know what it is saying). When I go all RTFM on this topic I usually tell them to 'man rsync', search for file-wil

Re: Yet another filter question

On Tue, May 3, 2016 at 1:07 PM, Christoph Biedl wrote: > + *.git/.git/* > - *.git/ > >From the man page near the start of the "INCLUDE/EXCLUDE PATTERN RULES" section: *Note that, when using the --recursive (-r) option (which is implied by > -a), every subcomponent of every path is visited f

Re: Yet another filter question

Try: + *.git/ + *.git/.git/*** - *.git/* (you probably want to add --prune-empty-dirs) Also, when debugging filters/excludes use -vv as it will tell you which pattern is causing it to do what. Also, there is no point in using -v without --itemize-changes. On 05/03/2016 04:07 PM, Christoph Biedl

Yet another filter question

Hello, Since the very first day I've been using rsync - some 15 years ago - the filtering rules caused great grieve. Their behaviour is just not the way I'd expect it be be and as I read the manpage. Usually I end up with some hand-written recipes, carefully documented,y including all the gotchas.

Re: Question on folder sync with "directory name translation"

Yeah, I don't have other symlink. But I'm thinking of changing my folder structure to reflect the data I really need on the NAS. So, as a side effect, the special rsync is not needed any more :) Anyway, thanks for the answers! Bye *___Gionata Boccalini* 2015-06-09 13:25 GMT+02:00 Mi

Re: Question on folder sync with "directory name translation"

Hello, I've been tasked with migrating a smallish (@90 mailboxes) company from a linux/dovecot mail server to Office 365, and after experiencing a ton of issues with Microsoft's native Imap syncing tool, I decided to use Imapsync, and it is working perfectly. It has the ability to add a simple re

Re: Question on folder sync with "directory name translation"

Should be as long as you don't have other symlinks in the tree. On Mon, Jun 8, 2015, 15:14 Gionata Boccalini wrote: > OK , but then the solution with symlinks is equivalent, just with the > right options for rsync. > > Make the link. > Sync + exclude. > Remove the link. > > Don't have to live wi

Re: Question on folder sync with "directory name translation"

OK , but then the solution with symlinks is equivalent, just with the right options for rsync. Make the link. Sync + exclude. Remove the link. Don't have to live with the folder on the source. *___Gionata Boccalini* 2015-06-08 22:49 GMT+02:00 Michael Johnson - MJ : > Oh, actually

Re: Question on folder sync with "directory name translation"

I should describe the problem more in details, but I believe this is off topic for this list. The FolderA is named "Musica" (in Italian) because.. I like it that way.. and is in my home folder. PC # /home/gionata/Musica FolderB MUST be named "music", in my home folder on the NFS filesystem, NAS

Re: Question on folder sync with "directory name translation"

The symlinks was mostly a shot in the dark. They're often useful when you need synonyms. The --fuzzy: I believe once handles different names and the second one adds different locations. I have thought about using it for issues I have reorganizing collections of media files, but never got aro

Re: Question on folder sync with "directory name translation"

Thanks Joe for the reply: 1) why do you say to use fuzzy twice? Do you mean in both directions? 2) I have to mention that the remote system is a Synology NAS, which for whatever reason (I can't think about), doesn't support symlinks, even in the same disk volume or "share"! > But I could make some

Re: Question on folder sync with "directory name translation"

I'm sure one of the experts will have a better answer, but two things come to mind as options to explore: 1) Use --fuzzy twice so files which are the same but possibly with different names and locations are synced 2) Use some sort of symlinks on the destination so the names actually match (these

Question on folder sync with "directory name translation"

Hello everyone, I'm new to this mailing list but I have been using rsync for some years up to now. I'm trying to synchronize two directory trees, but I want a special behavior that I didn't find on the net nor in the manual (or maybe there is a combination of options to get what I want but I could

Re: A question about CVE-2014-8242

On Mon, May 11, 2015 at 10:38 PM, yhu2 wrote: > Thanks your explanation, how about MD4 (rsync protocal <30)? any comment > would be appreciated!! > The MD4 checksum in older protocols doesn't have the issue. ..wayne.. -- Please use reply-all for most replies to avoid omitting the mailing list

Re: A question about CVE-2014-8242

wayne. Thanks your explanation, how about MD4 (rsync protocal <30)? any comment would be appreciated!! Thanks again. Yadi On 05/12/2015 05:19 AM, Wayne Davison wrote: On Mon, May 11, 2015 at 12:50 AM, yhu2 > wrote: whether or not CVE-2014-8242 affects rsy

Re: A question about CVE-2014-8242

Thanks great!!!. Yadi On 05/12/2015 05:19 AM, Wayne Davison wrote: On Mon, May 11, 2015 at 12:50 AM, yhu2 > wrote: whether or not CVE-2014-8242 affects rsync? any commnet would be appreciated!! Yes. It would be extremely hard for someone to trigger th

Re: A question about CVE-2014-8242

On Mon, May 11, 2015 at 12:50 AM, yhu2 wrote: > whether or not CVE-2014-8242 affects rsync? any commnet would be > appreciated!! > Yes. It would be extremely hard for someone to trigger that via indirect means (such as inserting DB data and managing to match a checksum record boundary in conte

A question about CVE-2014-8242

Hi,everyone here: whether or not CVE-2014-8242 affects rsync? any commnet would be appreciated!! Yadi -- 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.

--temp-dir option question/issue

Hello, I am using rsync with "--temp-dir=/tmp" option for rsync module. I noticed that if the "tmp" directory is deleted rsync attempt will fail like - rsync: mkstemp "/tmp/.xyz_file.Z0m8I6" (in ) failed: No such file or directory (2) rsync error: some files/attrs were not transferred (see prev

Re: question about output of files copied/deleted

Hi. On Wed, 16 Jul 2014 23:24:45 -0700 Don Cohen wrote: > So another question/suggestion - if you save the output it would be > nice to be able to pipe it back into rsync as the list of files to > be transferred - which would be easier if there were a switch to do > the trans

Re: question about output of files copied/deleted

is never an ambiguity in replacing \#NNN sequences in the output of filenames. Only full 5-char sequences are affected that way, so the decoding rule is as simple as: s/\\#(\d\d\d)/ chr(oct($1)) /eg; I see that now. So another question/suggestion - if you save the output it would be nice to be a

Re: question about output of files copied/deleted

On Wed, Jul 16, 2014 at 6:40 PM, Don Cohen wrote: > An output line like asd\#002\#003zxc could either mean a file of that name > or asd^B\#003zxc or asd^B^Czxc or asd\#002^Czxc > Did you test that theory? Give it a try and you'll discover that \# followed by 3 digits in a filename always encode

Re: question about output of files copied/deleted

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 The solution you are missing is that rsync can archive files itself using either --link-dest or --backup depending on whether you want a complete tree in the archive or not. On 07/16/2014 09:40 PM, Don Cohen wrote: > > It seems to me that this output

question about output of files copied/deleted

It seems to me that this output would be more useful if it were possible to uniquely translate a line of output back into a file path. Right now that's not possible due to the control character encoding. An output line like asd\#002\#003zxc could either mean a file of that name or asd^B\#003zxc or

Re: Question about --files-from= and folder structure

On Fri, Jan 3, 2014 at 12:39 PM, Bill Dorrian wrote: > The script that I'm running works - sort of - in that it syncs the files; > but it syncs their parent directories too, which I'm trying to avoid. --files-from implies -R (--relative), which tells rsync to include the path info. If you don't

Re: Question about --files-from= and folder structure

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I don't know of a simple solution that would work with both --delete and with any number of files but here is an idea... Make an additional folder and link all the mp3 files into it then rsync that folder... rm -rf /backup/Music.flat mkdir /backup/Mu

Question about --files-from= and folder structure

I'm writing a script to sync some mp3 files. Due to a limitation in the number of destination files that can be read from my thumb drive, I'm not looking to preserve the original file structure (actually, I'm looking to sync *only the files* to the new destination directory). The source files

Re: Question about rsyncing to a slightly different folder structure on target

On 2014-01-01 2:02 PM, Wayne Davison wrote: On Tue, Dec 31, 2013 at 3:59 AM, Charles Marcus mailto:cmar...@media-brokers.com>> wrote: On the old server, dovecot is configured to just use .../example.com/user for the maildirs. On the target server, I want

Re: Question about rsyncing to a slightly different folder structure on target

On Tue, Dec 31, 2013 at 3:59 AM, Charles Marcus wrote: > On the old server, dovecot is configured to just use .../example.com/userfor > the maildirs. > > On the target server, I want to change this to .../ > example.com/user/Maildir > One thing you can do is to add a symlink on the sending side

Question about rsyncing to a slightly different folder structure on target

Hi all, Ok, if this isn't possible with some kind of wildcard, I can adjust the target manually, but if I can just modify the command to allow for the different folder structure on the target, I'd rather do that. I'm incrementally rsync'ing my mailstore from the old server to the new server,

Re: Need hint for my question regarding the working of rsync.

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I wasn't saying I had millions of links of the same file. It was hundreds of link-dest backups some of which contained a few but not all that many links. I wasn't doing a link-dest backup of something link heavy. On 11/13/13 15:01, Karl O. Pinc wrot

Re: Need hint for my question regarding the working of rsync.

necessarily 11/13/2013 01:04:29 PM, Kevin Korb wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > Is there a hard links limit? I have been in the 70-80 million range > on ext4 without a problem (other than performance which is why I > switched to ZFS for that use case). It's a per-file

Re: Need hint for my question regarding the working of rsync.

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Is there a hard links limit? I have been in the 70-80 million range on ext4 without a problem (other than performance which is why I switched to ZFS for that use case). On 11/13/13 13:59, Karl O. Pinc wrote: > On 11/13/2013 12:03:21 PM, Kevin Korb wr

Re: Need hint for my question regarding the working of rsync.

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 To an extent it is serially. The sender tells the receiver what it needs to stat(). However, thanks to incremental indexing it will parallelize but the receiver will not go beyond what the receiver has sent. Read the --recursive section of the man p

Re: Need hint for my question regarding the working of rsync.

On 11/13/2013 12:03:21 PM, Kevin Korb wrote: > OK, in the case of using v3 with --link-dest and not --checksum most > of the initial activity on the sender would be doing calls to stat() > to index what is there. > > The receiving side would be doing 2x the stat() calls (you have 2 > --link-dest d

Re: Need hint for my question regarding the working of rsync.

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 OK, in the case of using v3 with --link-dest and not --checksum most of the initial activity on the sender would be doing calls to stat() to index what is there. The receiving side would be doing 2x the stat() calls (you have 2 - --link-dest dirs for

Re: Need hint for my question regarding the working of rsync.

>> These are both a weak and a strong checksum for each chunk of the file from start to finish. So lets take an example. If a file were 7 bytes and the logical block size for rsync by default being 700, it would send : 1) 4 Bytes x 7/700 = 400 Bytes 2) 16 Bytes x 7/700 = 1600 Bytes T

Re: Need hint for my question regarding the working of rsync.

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 First, are you talking about --checksum checksums or the hashing of files that are different on both ends so that only the differences need to be transferred? You seem to be talking about the latter while describing the performance of the former. If

Re: Need hint for my question regarding the working of rsync.

On 11/12/2013 04:13:01 PM, Karl O. Pinc wrote: > On 11/12/2013 03:50:20 PM, Wayne Davison wrote > > > Yes, the receiver sends all the checksums that it generates at once > > > For really big files it would be interesting to amend this rule to > > one > > where the sending side waits only long en

Re: Need hint for my question regarding the working of rsync.

On 11/12/2013 03:50:20 PM, Wayne Davison wrote > Yes, the receiver sends all the checksums that it generates at once > For really big files it would be interesting to amend this rule to > one > where the sending side waits only long enough for a certain number of > checksums to arrive before it

  1   2   3   4   5   6   7   >