https://bugzilla.samba.org/show_bug.cgi?id=10579
Wayne Davison changed:
What|Removed |Added
Resolution|--- |FIXED
Status|NEW
https://bugzilla.samba.org/show_bug.cgi?id=10579
Haravikk changed:
What|Removed |Added
Version|3.1.0 |3.1.3
--- Comment #1 from Haravikk ---
Just
https://bugzilla.samba.org/show_bug.cgi?id=10579
Summary: --xattr internal abbrev error
Product: rsync
Version: 3.1.0
Platform: All
OS/Version: Mac OS X
Status: NEW
Severity: major
Priority: P5
Component
That's the missing info I needed to fix the problem. There was a
call in the sender that was being run when it shouldn't have in dry-
run mode. The latest dev version (git, nightly, etc.) has this fixed.
And it looks like all the problems I was having are now resolved.
Many thanks to
On Mon, Feb 04, 2008 at 01:59:54AM +0100, Giuliano Gavazzi wrote:
Running without -n transfers the file correctly.
That's the missing info I needed to fix the problem. There was a call
in the sender that was being run when it shouldn't have in dry-run mode.
The latest dev version (git, nightly,
On 13 Jan 2008, at 08:06, Wayne Davison wrote:
On Sat, Jan 12, 2008 at 08:29:43PM +, Max Lane wrote:
[receiver] internal abbrev error!
Aha, I fixed on on the sending side, but yours is on the receiving
side.
I just checked-in a change that should hopefully fix that too. If you
could
On Sun, 2008-01-13 at 11:31 +, Max Lane wrote:
I'm still getting the error with rsync-HEAD-20080113-0640GMT:
sync: writefd_unbuffered failed to write 5 bytes [sender]: Broken pipe
(32)
[receiver] internal abbrev error! len=61 datum[0]=98
rsync: connection unexpectedly closed (52620
On 13/01/2008, Wayne Davison [EMAIL PROTECTED] wrote:
On Sat, Jan 12, 2008 at 08:29:43PM +, Max Lane wrote:
[receiver] internal abbrev error!
Aha, I fixed on on the sending side, but yours is on the receiving side.
I just checked-in a change that should hopefully fix that too. If you
On Wed, Jan 09, 2008 at 12:22:27PM -0800, Wayne Davison wrote:
I have an idea of what may be the problem, and will check into it
soon.
The latest dev version now has this fixed, including git nightly tar
file. Thanks for the report!
..wayne..
--
To unsubscribe or change options:
rsync: writefd_unbuffered failed to write 5 bytes [sender]: Broken pipe (32)
[receiver] internal abbrev error!
rsync error: error in rsync protocol data stream (code 12) at xattrs.c(565)
[receiver=3.0.0pre8]
rsync: connection unexpectedly closed (51836 bytes received so far) [sender]
rsync error
On Sat, Jan 12, 2008 at 08:29:43PM +, Max Lane wrote:
[receiver] internal abbrev error!
Aha, I fixed on on the sending side, but yours is on the receiving side.
I just checked-in a change that should hopefully fix that too. If you
could give the latest dev version a try, I'd like to know
Hello,
I'm trying the latest rsync(3.0.0prev7) on Mac OS 10.5.1 and getting the
following error:
rsync: writefd_unbuffered failed to write 887 bytes [sender]: Broken pipe
(32)
recv_xattr_request: internal abbrev error!
rsync: connection unexpectedly closed (26242 bytes received so far) [sender
On Wed, Jan 09, 2008 at 09:41:33AM +, Max Lane wrote:
Can someone explain what an internal abbrev error is?
The internal code that that is trying to request the contents of a large
xattr value from the sender is confusing the receiver somehow. I have
an idea of what may be the problem
13 matches
Mail list logo
