I want to recognize and handle some rsync error messages
in my log files (containing also the --itemize-changes output)
on different computers with different language/locale settings.
Can I rely on rsync to create only English error messages
to have a stable pattern to recognize?
PS: In the
On Thu, 2023-12-14 at 14:09 -0500, Kevin Korb wrote:
> Unfortunately, exit 23 litterally just means something else went wrong
> and might have scrolled off of the screen if you have rsync listing
> files (--verbose or --itemize_changes). Essentially, it is anything
> that doesn't have its own
I am trying to find a solution for the open source Linux software
"Back In Time" (https://github.com/bit-team/backintime)
where we evaluate the rsync exit code when taking a backup via rsync
and inform the user that an error has occured.
Questions:
1. Is there full list of possible reasons
Here is the missing attachment ;-)
On Fri, 2023-09-22 at 21:01 +0200, rsync--- via rsync wrote:
> On Fri, 2023-09-22 at 07:37 -0400, Kevin Korb wrote:
> > So I decided to do a quick test using the Linux kernel source tree since
> > it has lots of files.
>
> Excellent idea
On Fri, 2023-09-22 at 07:37 -0400, Kevin Korb wrote:
> So I decided to do a quick test using the Linux kernel source tree since
> it has lots of files.
Excellent idea using kernel sources! A lot of different files...
I will use this to create indicative benchmarks for different scenarios...
>
On Thu, 2023-09-21 at 20:08 -0400, Kevin Korb via rsync wrote:
> I have heard in the past that rsyncing an empty dir over a tree to
> delete the tree is faster than an rm -rf but I can't say I have ever
> benchmarked it to get any actual numbers.
This **may** indeed be a myth (for a long time
Context
---
I am one of the active developers of the open source application "Back in Time"
which uses "rsync" as backend and I want to fix an open issue:
"Back in Time"-Bug:
https://github.com/bit-team/backintime/issues/994#issuecomment-1724211507
"Back in Time" uses "--link-dest"
Rainy Days via rsync wrote:
> Hi,
>
> My company have been using rsync to sync our file to a backup server (running
> rsync daemon), and now we would like to store them encrypted.
> I found some thread that discussed this issue but they are pretty old (about
> 10 years ago). So I send this
Hallo Hannes
"man 5 crontab" is your friend ;-)
Am 12.07.2019 um 10:56 schrieb Hannes Hutmacher via rsync:
But, when I add the script in cron to start it at 1am at night it
takes 7 - 9 hours and I see up to 180 processes. When I look in top I
see a hight load of 60 - 80 and 40 - 60 waits.