Il 2025-07-30 14:26 Hardy via rsync ha scritto:
So NOT using --inplace will save a lot of network transmission at the
cost of local disk copying. Can you not tolerate the temporary disk
space?
Not in this case: for large file transfer (think about 40+ GB), this
would cause excessive load on
so I cannot check, but I suspect the --inplace to be
the culprit. If rsync has to overwrite the file while transferring, it may not
be able to check blocks in the original?
Regards
Hardy
--
I'm so stupid today, I could rule America.
On 29.07.25 12:55, Gionatan Danti via rsync wrote:
Hi
Il 2025-07-30 08:49 Hardy via rsync ha scritto:
Hi Danti,
away from my computer now, so I cannot check, but I suspect the
--inplace to be the culprit. If rsync has to overwrite the file while
transferring, it may not be able to check blocks in the original?
Regards
Hardy
Hi, I tried with
12:55, Gionatan Danti via rsync wrote:
Hi all,
rsync seems slow to copy large files. The issue is not related to the transfer
itself, which is quite fast, but to the discovery of different blocks.
For example, transferring a big (multi-GB) file from src (remote) to dst (local) with
"--inplace&
Hi all,
rsync seems slow to copy large files. The issue is not related to the
transfer itself, which is quite fast, but to the discovery of different
blocks.
For example, transferring a big (multi-GB) file from src (remote) to dst
(local) with "--inplace" (to avoid a whole-file copy on dst) s
Hi. I’m hoping this is the right place to send this. My sincerest
apologies if it’s not.
I have a small patch that I'm hoping might be considered for inclusion
in a future release of rsync. It relates to the retention of permissions
when copying symbolic links.
On most systems, permissions for a
Hello to everyone.
I'm trying to copy all the system files of Rocky Linux 9 from within
Ubuntu-2404-KDE6-Wayland vm to outside the vm,directly on the UFS fs of
FreeBSD 14.2 using this command :
rsync -avxHAXP * /FreeBSD/compat/linux
but I get a lot of errors :
/include/config/.PINCTRL_ELKHARTLA
On 05 May 2025, at 20:14, Derek Martin wrote:
> If I understand correctly, I believe using --chmod without using
> --perms (or with --no-p) will do what you want. Typical command lines
> often use -a which equates to -rlptgoD (i.e. it includes -p/--perms).
> So you either need to not use -a and
On Tue, Apr 08, 2025 at 12:54:24PM +0100, Graham Leggett via rsync wrote:
> I misunderstood the --chmod option, thinking that it specified the
> permissions at the destination. What actually happens is that it
> overrides the source permissions, and has a side effect of the
>
On 21 Apr 2025, at 06:37, TheNew HEROBRINE via rsync
wrote:
> For your situation I think you should use both --fake-super and -M--super
> because reading the manual it says:
> "For a local copy, this option affects both the source and the destination.
> If you wish a local co
For your situation I think you should use both --fake-super and -M--super
because reading the manual it says:
"For a local copy, this option affects both the source and the destination.
If you wish a local copy to enable this option just for the destination
files, specify -M--fake-super. If you wis
On 08 Apr 2025, at 12:54, Graham Leggett via rsync
wrote:
> Another thing I've found is that my backups have lost their permissions.
>
> I misunderstood the --chmod option, thinking that it specified the
> permissions at the destination. What actually happens is that it
Hi all,
I have a backup that was created with --fake-super that I need to restore to a
fresh partition on the same machine as the backup (source and destination on
the same machine).
The docs describe how --fake-super is used to make the backup, but none of the
docs describe how you do the rev
On 08 Apr 2025, at 10:28, Graham Leggett via rsync
wrote:
> Unfortunately all combinations of --fake-super that I have used so far have
> had the effect of backing up the backup, not restoring the backup.
Looking in the source code, it looks like the difference between rsync
perfor
On 08 Apr 2025, at 10:04, Paul Slootman via rsync wrote:
>> I have a backup that was created with --fake-super that I need to restore to
>> a fresh partition on the same machine as the backup (source and destination
>> on the same machine).
>>
>> The docs descri
Hi all,
Another thing I've found is that my backups have lost their permissions.
I misunderstood the --chmod option, thinking that it specified the permissions
at the destination. What actually happens is that it overrides the source
permissions, and has a side effect of the destination permiss
On Tue 08 Apr 2025, Graham Leggett via rsync wrote:
>
> I have a backup that was created with --fake-super that I need to restore to
> a fresh partition on the same machine as the backup (source and destination
> on the same machine).
>
> The docs describe how --fake-super i
some Makefile tweaking?
>
>On 3/3/25 9:55 PM, Randall S. Becker via rsync wrote:
>> 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.
d-linux-x86-64.so.2 (0x7f77c9259000)
$ uname -a
Linux fog 5.15.0-133-generic #144-Ubuntu SMP Fri Feb 7 20:47:38 UTC 2025
x86_64 x86_64 x86_64 GNU/Linux
Maybe whatever mystery platform you are on needs some Makefile tweaking?
On 3/3/25 9:55 PM, Randall S. Becker via rsync wrote:
On March 3, 2
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 onl
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
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
I have a backup job failing because of a long path with error message
(full output below, [1]):
> overflow: xflags=0x2078 l1=255 l2=775 lastname=long path
> ERROR: buffer overflow in recv_file_entry [receiver]
It looks like the remote system (a Hetzner Storagebox) for some reason
has a ma
Dear Stein,
Thanks for the suggestions and link to your patch.
Indeed it's quite related to scenarios I'm having with large scale
audiovisual collection synchronizations in memory institutions.
My request here on this list however goes beyond "something I can get to
work in my setup":
Even t
r (or the same) patch if you give me a month of time,
> never mind the money. A month includes overhead & a nice profit, I really
> need the time ;-).
>
> Cheers, hope this will work for you!
>
> Stein Haugan
>
>> On 15 Feb 2025, at 21:24, Peter B. via rsync w
same) patch if you give me a month of time,
never mind the money. A month includes overhead & a nice profit, I really need
the time ;-).
Cheers, hope this will work for you!
Stein Haugan
> On 15 Feb 2025, at 21:24, Peter B. via rsync wrote:
>
> Hello everyone :)
>
>
7;m really professionally interested in such a feature, as it would
greatly make our lives in the galleries-libraries-archives-museums
(GLAM) world :D
Thank you very much in advance!
Peter B.
On 11.12.24 17:17, Peter B. via rsync wrote:
On 12/10/24 21:15, Roland Kletzing wrote:
hello,
that
Hi all,
for an rsync-based incremental mechanism we use quite some pre- and
post-processing through pre-xfer and post-xfer. However it has turned
out, that the pre- and post-processing scripts must be able to differ
between uploads and downloads, as we require different processing steps
in either
* "rsync.project via rsync"
:
Wrote on Wed, 15 Jan 2025 09:34:10 +1100:
> sorry about the prefix changes in rsync-patches. We're going to be dropping
> the whole rsync-patches system soon anyway, as it really isn't working
> well. It was supposed to be a staging ar
> 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
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I don't believe the transferring part of rsync will jump around. 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.
O
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
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
There is no guarantee that rsync will do anything in any order since it
is going by the filesystem without any sorting. With --delete-during
the directory indexing and therefore the deletions are running in
parallel with file transfers. This means i
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 order it does things
> in. I
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
On Thu, 2025-Jan-16, BP via rsync wrote:
I always run rsync as follows: "sudo rsync -PaSHAXvi --del DIR1/
DIR2". I would think that whenever I see in the output of this rsync
command a few lines of the form A/B/... and then further down in the
output again a few lines of the form A/B
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 rsync
command a few lines of the form A/B/... and then further down in the
output again a few lines of the form A/B/... (dots are dirs or files),
then every line b
rsbecker@... asks:
>> Is there a way I can get access to a machine 3.4.0 is failing to build on?
>> Maybe a VM under VirtualBox? Or some cloud service?
>> I don't have an ia64
QEMU does not support IA-64, so VMs are likely out. 20+ years ago, HP
had an IA-64 emulator that sort of worked, but did
Due to some regressions in 3.4.0 we have released 3.4.1.
See https://download.samba.org/pub/rsync/NEWS#3.4.1 for details of the
changes
Our apologies for not catching these issues before 3.4.0
--
Please use reply-all for most replies to avoid omitting the mailing list.
To unsubscribe or change opt
t; Is there a way I can get access to a machine 3.4.0 is failing to build on?
> Maybe a VM under VirtualBox? Or some cloud service?
>
> I don't have an ia64
>
>
>
> On Thu, 16 Jan 2025 at 01:20, wrote:
>
> On January 14, 2025 11:20 PM, Perry Hutchison wrote:
>
rsbec...@nexbridge.com> > wrote:
On January 14, 2025 11:20 PM, Perry Hutchison wrote:
>"Randall S. Becker via rsync" <mailto:rsync@lists.samba.org> > wrote:
>
>> FYI: I think this is just missing #include "rsync.h" in popt/findme.c
>
>Structurally, t
>"Randall S. Becker via rsync" <mailto:rsync@lists.samba.org> > wrote:
>
>> FYI: I think this is just missing #include "rsync.h" in popt/findme.c
>
>Structurally, this seems very odd. I thought popt was a generic argument
handler,
>which should not nee
Is there a way I can get access to a machine 3.4.0 is failing to build on?
Maybe a VM under VirtualBox? Or some cloud service?
I don't have an ia64
On Thu, 16 Jan 2025 at 01:20, wrote:
> On January 14, 2025 11:20 PM, Perry Hutchison wrote:
> >"Randall S. Becker via rsync&qu
On January 14, 2025 11:20 PM, Perry Hutchison wrote:
>"Randall S. Becker via rsync" wrote:
>
>> FYI: I think this is just missing #include "rsync.h" in popt/findme.c
>
>Structurally, this seems very odd. I thought popt was a generic argument
handler,
>whi
om: rsync mailto:rsync-boun...@lists.samba.org> > On Behalf Of Randall S. Becker via
rsync
Sent: January 14, 2025 6:46 PM
To: 'rsync.project' mailto:rsync.proj...@gmail.com> >
Cc: rsync@lists.samba.org <mailto:rsync@lists.samba.org>
Subject: RE: new release 3.4.0
> patch also.
>>
>>
>>
>> Thanks,
>>
>> Randall
>>
>>
>>
>> *From:* rsync *On Behalf Of *Randall S.
>> Becker via rsync
>> *Sent:* January 14, 2025 6:46 PM
>> *To:* 'rsync.project'
>> *Cc:* rsync@lists.
Another issue here in findme.c. strlcpy() is a BSD-only method and
> definitely not portable.
>
> Please consider other platforms when creating patches. I can provide a
> patch to this
>
> patch also.
>
>
>
> Thanks,
>
> Randall
>
>
>
> *From:* rsy
"Randall S. Becker via rsync" wrote:
> FYI: I think this is just missing #include "rsync.h" in popt/findme.c
Structurally, this seems very odd. I thought popt was a generic
argument handler, which should not need to #include details of the
application that is using it
ue here in findme.c. strlcpy() is a BSD-only method and definitely
not portable.
Please consider other platforms when creating patches. I can provide a patch to
this
patch also.
Thanks,
Randall
From: rsync mailto:rsync-boun...@lists.samba.org> > On Behalf Of Randall S. Becker via
rsy
Another issue here in findme.c. strlcpy() is a BSD-only method and definitely
not portable.
Please consider other platforms when creating patches. I can provide a patch to
this
patch also.
Thanks,
Randall
From: rsync On Behalf Of Randall S. Becker via
rsync
Sent: January 14, 2025 6
I don't have a Mac to test on. If you have a Mac maybe you could test and
open a PR against rsync for the change?
On Wed, 15 Jan 2025 at 10:12, Ryan Carsten Schmidt
wrote:
> On Jan 14, 2025, at 16:34, rsync.project wrote:
>
>
> sorry about the prefix changes in rsync-patches.
>
>
> No problem;
ully ask that it be included ASAP.
Thanks,
Randall
From: rsync On Behalf Of Randall S. Becker via
rsync
Sent: January 14, 2025 6:09 PM
To: 'rsync.project'
Cc: rsync@lists.samba.org
Subject: RE: new release 3.4.0 - critical security release
This happens on NonStop x86 and ia64. I h
On Jan 14, 2025, at 16:34, rsync.project wrote:sorry about the prefix changes in rsync-patches.No problem; those changes were easy to remove from the fileflags patch. We're going to be dropping the whole rsync-patches system soon anyway, as it really isn't working well. It was supposed to be a stag
is not portable. Is there
a way around this?
Thanks,
Randall
From: rsync mailto:rsync-boun...@lists.samba.org> > On Behalf Of rsync.project via rsync
Sent: January 14, 2025 2:49 PM
To: rsync-annou...@lists.samba.org <mailto:rsync-annou...@lists.samba.org>
Cc: rsync@lists.samba
sorry about the prefix changes in rsync-patches. We're going to be dropping
the whole rsync-patches system soon anyway, as it really isn't working
well. It was supposed to be a staging area where users would test the
patches before being considered for the main release, but we haven't really
receiv
The patches within the rsync-patches-3.4.0.tar.gz archive seem to contain new
unnecessary hunks that change the prefix from /usr to /usr/local. This was not
the case in 3.3.0.
I use the fileflags.diff patch in the MacPorts build of rsync, and with the
3.4.0 version of this patch, it does not b
; *From:* rsync *On Behalf Of *rsync.project
> via rsync
> *Sent:* January 14, 2025 2:49 PM
> *To:* rsync-annou...@lists.samba.org
> *Cc:* rsync@lists.samba.org
> *Subject:* new release 3.4.0 - critical security release
>
>
>
> We have just released version 3.4.0 of rsync. Thi
A new dependency was added since 3.3, alloca(), which is not portable. Is there
a way around this?
Thanks,
Randall
From: rsync On Behalf Of rsync.project via rsync
Sent: January 14, 2025 2:49 PM
To: rsync-annou...@lists.samba.org
Cc: rsync@lists.samba.org
Subject: new release 3.4.0
"rsync.project via rsync" writes:
> We have just released version 3.4.0 of rsync. This release fixes 6 security
> vulnerabilities found by two
> groups of security researchers.
>
> You can find the new release links here:
>
> - https://rsync.samba.org/
> - ht
We have just released version 3.4.0 of rsync. This release fixes 6 security
vulnerabilities found by two groups of security researchers.
You can find the new release links here:
- https://rsync.samba.org/
- https://download.samba.org/pub/rsync/src/
For details on the vulnerabilities please see
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 r
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
&g
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
IX path is:
/c/user/snapshots/rsync_test/last
I've tried:
--link-dest=snapshots/rsync_test/last
--link-dest=./snapshots/rsync_test/last
--link-dest=../last
but none seem to work.
Thanks,
Tony
On Sat, Jan 11, 2025 at 9:02 PM Kevin Korb via rsync
wrote:
>
> rsyncd doesn't t
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 rsyn
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
On 24.12.24 09:53, Mario Marietto via rsync wrote:
There are times when a large file is copied up to 99% and then deleted after
having received the error. Other times when the error occurs earlier and only a
part of it is copied. Does it make sense to calculate the checksum if in both
cases
On 23.12.24 22:06, Mario Marietto wrote:
-> Did you re-read the data and compare checksums ?
Don't know how to do this.
Files can be considered binary identical if they do have the same checksums.
e.g.
# md5sum [files]
Using windows:
https://windowsreport.com/checksum-on-windows/
c:certu
>
> https://stackoverflow.com/questions/478722/what-is-the-best-way-to-calculate-a-checksum-for-a-file-that-is-on-my-machine
>
> On Mon, Dec 23, 2024 at 11:02:21PM +0100, Mario Marietto via rsync wrote:
> > -> Are you running windows on the same hardware as Linux/BSD ? Is it
If you have different systems for windows vslinux, it's possible there is
> a HW issue with one of them.
>
>
> Tom
>
>
> On 24 December 2024 7:44:16 am GMT+12:00, Mario Marietto via rsync <
> rsync@lists.samba.org> wrote:
>
>> What would you think if I t
Mario,
Are you running windows on the same hardware as Linux/BSD ? Is it a dual-boot
system?
If you have different systems for windows vslinux, it's possible there is a HW
issue with one of them.
Tom
On 24 December 2024 7:44:16 am GMT+12:00, Mario Marietto via rsync
wrote:
> Wh
4 and ZFS) that interferes with
the transfers of big files. Maybe a disk driver of some sort.
On Mon, Dec 23, 2024 at 10:54 PM Hardy via rsync
wrote:
>
> On 23.12.24 20:44, Mario Marietto via rsync wrote:
> > What would you think if I told you that using Windows I no longer had
>
On 23.12.24 20:44, Mario Marietto via rsync wrote:
What would you think if I told you that using Windows I no longer had that
problem ?
Would you still think that there are hardware problems ?
And if so, why would they only manifest themselves using Linux and FreeBSD and
not using Windows
ng Windows 11 because I want
> to
> > > exclude some variables from the equation.
> > >
> > > On Mon, Dec 23, 2024 at 7:49 PM Robin Lee Powell <
> > > rlpow...@digitalkingdom.org> wrote:
> > >
> > >> Almost certainly your drive is going ba
On Linux I'd tell you to
>> check dmesg for drive errors, I don't know what the FreeBSD
>> equivalent is. But I strongly recommend that you treat that drive
>> as "going to fail any second".
>>
>> On Mon, Dec 23, 2024 at 12:56:09PM +0100, Mario Mari
ivalent is. But I strongly recommend that you treat that drive
> as "going to fail any second".
>
> On Mon, Dec 23, 2024 at 12:56:09PM +0100, Mario Marietto via rsync wrote:
> > Using the parameters below the file hasn't been removed at 100% even if I
> > got the
sually happens before
>> rsync,that is able to complete the transfer until 99%.
>> I've detached and reattached the USB disks,but I still see the error.
>>
>> On Mon, Dec 23, 2024 at 11:07 AM Paul Slootman via rsync <
>> rsync@lists.samba.org> wrote:
>>
&
O error at some point.
>
> Yes,I tried cp and I got the same error,that usually happens before
> rsync,that is able to complete the transfer until 99%.
> I've detached and reattached the USB disks,but I still see the error.
>
> On Mon, Dec 23, 2024 at 11:07 AM Paul Slootman via rsy
nd reattached the USB disks,but I still see the error.
On Mon, Dec 23, 2024 at 11:07 AM Paul Slootman via rsync <
rsync@lists.samba.org> wrote:
> On Mon 23 Dec 2024, Mario Marietto via rsync wrote:
> >
> > Everytime I try to copy a file from one USB disk to another one (does no
On Mon 23 Dec 2024, Mario Marietto via rsync wrote:
>
> Everytime I try to copy a file from one USB disk to another one (does not
> matter which one),I get this kind of error :
>
>
> mario@Z390-AORUS-PRO-DEST:/mnt/zroot-133/A_FILES/Backup/FreeBSD# rsync
> -avxHAX
Hello.
Everytime I try to copy a file from one USB disk to another one (does not
matter which one),I get this kind of error :
mario@Z390-AORUS-PRO-DEST:/mnt/zroot-133/A_FILES/Backup/FreeBSD# rsync
-avxHAXP FreeBSD-141-UFS-sdc-DarkMatter.img
/mnt/sdj1/OS/Backup/BSD/FreeBSD --ignore-existing
send
Dear Roland,
On 12/10/24 21:15, Roland Kletzing wrote:
hello,
that sounds interesting - just one question: what about file size? is
it always zero or is it set to the original size and the file contents
are empty ?
The filesize (IMO) should stay 0 bytes, since the file actually /is/ empty.
I
Hi everyone :)
I'm professionally and seriously working with extended filesystem
attributes (xattrs) for search/retrieval of data.
I am making a "thincopy" of large data trees, like this:
`$ cp --attributes-only --preserve=all $(SOURCE) $(TARGET)`
Is there a way to do this with rsync?
I'm a
On 12/9/24 23:46, Perry Hutchison wrote:
Sounds as if the catb.org domain registration expired and got bought
by someone unrelated to the original owner. The wonder is that the
previous content is still there.
It seems that "catb.org" really is Eric's personal site, and the issue
is solely wh
.
On 12/9/24 17:11, Peter B. via rsync wrote:
Hi everyone :)
On the [official website regarding rsync mailing lists](https://
rsync.samba.org/lists.html), the text contains a link:
"but please [read this before posting]"
Which points to:
https://www.catb.org/~esr/faqs/smart-ques
"Peter B. via rsync" wrote:
> On the [official website regarding rsync mailing
> lists](https://rsync.samba.org/lists.html), the text contains a link:
>
> "but please [read this before posting]"
>
> Which points to:
> https://www.catb.org/~esr/faq
Hi everyone :)
On the [official website regarding rsync mailing
lists](https://rsync.samba.org/lists.html), the text contains a link:
"but please [read this before posting]"
Which points to:
https://www.catb.org/~esr/faqs/smart-questions.html
Which throws a "bad_domain_error" SSL error, list
I found this helpful re /3:
https://serverfault.com/questions/373058/comparing-owners-and-permissions-of-content-of-two-folders
If there's any gotchas that jump out - jump on in.
M
On 08/12/2024 2:28 pm, Morgan Read wrote:
Hello List,
I've been running rsync for must be 20 years by now, but ov
Hello List,
I've been running rsync for must be 20 years by now, but over that time
the holes in the Swiss cheese that passes for my brain seem to have
grown larger and been filled with budgie seed and sawdust.
I once used rsync as my regular backup solution but now settle for a
borg backend
k/mac/
On Fri, Nov 15, 2024 at 04:08:27PM +, Maxim Usatov via rsync wrote:
Dear All,
Having weird rsync issues after upgrading FreeBSD from 13.2 to 14.1 and
rsync along with it. I cannot find any solution. Setup: doing rsync backup
from the root ZFS to an SSD mounted to /media/da0p1. The rsy
On Sat, Nov 16, 2024 at 08:26:47AM GMT, Maxim Usatov via rsync wrote:
> Tried without nice, xattrs, acls and hard-links - same error.
Hmm okay, a real bug then :-) It likely has to do with the way cron
assumes the identity of the crontab owner. I would ask on the
freebsd-questions list. It
Hi Ian,
Tried without nice, xattrs, acls and hard-links - same error.
Regards,
Maxim Usatov
On 11/15/24 17:42, Ian Z via rsync wrote:
On Fri, Nov 15, 2024 at 04:08:27PM GMT, Maxim Usatov via rsync wrote:
I assume code 13 is related to permissions, but given rsync is
started as root, why
On Fri, Nov 15, 2024 at 04:08:27PM GMT, Maxim Usatov via rsync wrote:
> I assume code 13 is related to permissions, but given rsync is
> started as root, why would this happen? The same rsync commands
> worked on all previous versions of FreeBSD. It also fails with the
> same error
Dear All,
Having weird rsync issues after upgrading FreeBSD from 13.2 to 14.1 and
rsync along with it. I cannot find any solution. Setup: doing rsync
backup from the root ZFS to an SSD mounted to /media/da0p1. The rsync is
initiated as root using /etc/crontab. The log:
2024/11/15 08:30:01 [6
quivalent to: rsync -avh src dst .
>
> IOW, you're copying src and dst to the current directory.
>
> So, no, not a bug. Although --exclude throwing a warning when its
> argument starts with - would perhaps be reasonable.
>
> On Tue, Oct 29, 2024 at 08:30:31PM +0200, Ma
Hello,
Came across the following "sudo rsync -avh src/ dst --delete --exclude
--exclude ." this will apparently delete everything in the current dir except
for the dst dir, is this a bug?
rsync version 3.2.7 protocol version 31
Best regards
Mark--
Please use reply-all for most replies to avo
https://bugzilla.samba.org/show_bug.cgi?id=6741
--- Comment #7 from Marc Aurèle La France ---
Created attachment 18484
--> https://bugzilla.samba.org/attachment.cgi?id=18484&action=edit
rsync stdout filter
Checkpoint III
--
You are receiving this mail because:
You are the QA Contact for the
Paul Slootman via rsync wrote:
> On Wed 16 Oct 2024, Chris Green via rsync wrote:
> >
> > I use it almost exclusively on Linux systems and it would be really
> > handy if I could set a number of options which would always be used
> > when I run rsync. These would be
On Wed 16 Oct 2024, Chris Green via rsync wrote:
>
> I use it almost exclusively on Linux systems and it would be really
> handy if I could set a number of options which would always be used
> when I run rsync. These would be in addition to -a which is useful
> but not quite
Hi,
This is mostly intended for the maintainers to read.
What's intended way to actually get patches merged into rsync?
I've tried:
- Mailing list posts
- GitHub PRs
--ignore-non-existing-directory
https://lists.samba.org/archive/rsync/2015-November/030455.html
https://github.com/RsyncProject/r
1 - 100 of 2104 matches
Mail list logo
