Warren,
Just want to say thanks. I have my automated backups going now. Good
old cronie.
Since I have a cat6 line to my neighbor (as a favor for their net
access), I only have to move the backup box to his house and I have
off-site backups for $150 outlay (arm SOC and 4 TB drive) and
On Aug 3, 2018, at 10:17 AM, Warren Young wrote:
>
> It’s possible this behavior changed since I last looked at it.
It looks like the rsync version shipping with CentOS 7 will actually complain
if multiple target directory levels are missing. With only ~/tmp existing on
the target machine,
Warren, Thanks!
On 08/03/2018 12:17 PM, Warren Young wrote:
On Aug 3, 2018, at 9:59 AM, Robert Moskowitz wrote:
You haven’t needed "-e ssh” since rsync 2.6.0, which made it the default. It
was released in 2004.
How do I specify -p and -l that I cut out of my example?
Add it to
On Aug 3, 2018, at 9:59 AM, Robert Moskowitz wrote:
>
>> You haven’t needed "-e ssh” since rsync 2.6.0, which made it the default.
>> It was released in 2004.
>
> How do I specify -p and -l that I cut out of my example?
Add it to ~/.ssh/config:
Host nevia.htt-consult.com
Port
On 08/03/2018 11:07 AM, Warren Young wrote:
On Aug 3, 2018, at 8:57 AM, Robert Moskowitz wrote:
I seem to have an rsync versioning problem.
Have you ruled out the other causes of that error? For instance:
https://askubuntu.com/a/716911
yeah. It is backups, not backup. Oops.
On Aug 3, 2018, at 8:57 AM, Robert Moskowitz wrote:
>
> I seem to have an rsync versioning problem.
Have you ruled out the other causes of that error? For instance:
https://askubuntu.com/a/716911
> And researching this it comes down to a versioning issue.
That seems rather unlikely for
I seem to have an rsync versioning problem.
The sender is an old ClearOS6 server with rsynv 3.0.6
The receiver is a brand new Centos7-armv7 server with rsync 3.1.2
I am running rsync over ssh
Got the error:
rsync error: error in rsync protocol data stream (code 12) at io.c(600)
7 matches
Mail list logo
