- Original Message -
From: "Bob Hutchinson" <[EMAIL PROTECTED]>
To:
Sent: Friday, February 03, 2006 2:11 PM
Subject: Re: rsync Corrupted MAC on input.
On Friday 03 Feb 2006 19:56, Gary P wrote:
I am doing a large and long transfer and twice now i have gotten this
error
killing the
Hello,
I am trying to estimate the number of users I can hold on my rsync
backup server if all users are connecting at about the same time. I am
using rsync over ssh with 256bit-aes encryption. Here are my average
server specs (from least powerful to most powerful):
2.8GHz P4
1GB Ram
1
https://bugzilla.samba.org/show_bug.cgi?id=3304
[EMAIL PROTECTED] changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|
On Friday 03 Feb 2006 19:56, Gary P wrote:
> I am doing a large and long transfer and twice now i have gotten this error
> killing the transfer, anyone know what/how i can fix this?
>
>
>
> [EMAIL PROTECTED] [/etc/rsync]# Received disconnect from 66.160.191.130: 2:
> Corrupted MAC on input. rsync:
https://bugzilla.samba.org/show_bug.cgi?id=3479
[EMAIL PROTECTED] changed:
What|Removed |Added
Severity|normal |enhancement
Status|NEW
I am doing a large and long transfer and twice now
i have gotten this error killing the transfer, anyone know what/how i can fix
this?
[EMAIL PROTECTED]
[/etc/rsync]# Received disconnect from 66.160.191.130: 2: Corrupted MAC on
input.rsync: writefd_unbuffered failed to write 4 bytes: p
Hi, I'm using rsync with link-dest to make snapshot like backups into
/sawmill/backup/{hostname}/snapshot/{timestamp}/{root}
I'm getting warnings that I don't understand...
On Fri, Feb 03, 2006 at 05:00:01AM -, Cron Daemon wrote:
>+ rsync --recursive --links --perms --times --group --owner -
https://bugzilla.samba.org/show_bug.cgi?id=3479
Summary: Request: timestamps in --log-format
Product: rsync
Version: 2.6.7
Platform: Other
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P3
Compone
--On Wednesday, February 01, 2006 7:47 PM -0700
[EMAIL PROTECTED] wrote:
--- Comment #4 from [EMAIL PROTECTED] 2006-02-01 19:47 MST ---
OK, I just checked in some changes that make rsync use sigaction() and
sigprocmask() if they are available (otherwise signal() continues to be
used).
