Part of the genius of Linux is the concept that each tool should do one
thing well and with pipes it is extremely easy to chain these tools
together in combinations unique to the current requirements of any task.
I can't speak for the rsync developers, but I don't believe they would be
open to add
Once you have the closest superset of what you want to see in your rsync
output, run the result through a filter to clean it up before sending it.
sed and awk are great for this, but any language/script you are familiar
with will do. Having regexes for the pattern matching will make the job
easier
I am using the 'backup to a central backup server with 7 day
incremental' example to archive three separate computers to identically
configured (apart from name) shares on a Western Digital 'MyBookLive'
NAS which has rsync enabled. The backup from two Raspberry Pi Computers
operates without a p
If there isn't a huge list of files, you could use a bash script:
use ls or find to create a list of files on server 1 followed by a list
of files on server 2
run it through sort -u to eliminate duplicates
use ls or find to make a list of files on server 3
use diff to get lines only in server 3 (s
If you are doing a small test run that duplicates the problem, you could
use inotifywait or tail -f to watch the log in real time on another
terminal. Maybe you'd see something like a line being overwritten, etc.
I don't know what rsync would do with a file name that ends in a
carriage return (not
On 7/12/19 4:56 AM, Hannes Hutmacher via rsync wrote:
> Hi all! :-)
>
> I have a small rsync script to sync my data to a usb-disk. It works
> fine, when I start it in console. I get 3 rsync processes (look in
> top) and the backup takes ~25 min. But, when I add the script in
> cron to start it at
I brought this up on the list years ago and was told it's a feature, not
a bug.
Even if some other GNU or Linux commands have this "feature", it still
violates the principle of least surprise.
It's also pretty hard to discover because a null argument is literally
invisible.
Joe
On 4/17/19 9:54
While a solution using rsync would be ideal, if you don't have a huge
number of files or lots of huge files which meet this special case, it
probably wouldn't be prohibitively difficult to write your own special
case script.
It could be set to ignore all files that rsync will handle normally (but
I'm not sure if this might be an issue here. Since your variable isn't
quoted, it might not be. But:
When you run rsync as rsync $param1 ...
and param1 is null, it may still be treated as the first argument to
rsync - which may add the current directory to your sources or throw
things off in
