similar to: unexpected read size of 0 in map_ptr (Solaris 2.5.1)

We're using rsync to mirror a web server. The rsync is initiated using ssh from a Red Hat Linux 7.2 box, the files are located on an Alpha running a version of Digital Unix 4. On the Alpha rsync is 2.5.2, The Linux box used to have a 2.4.6-X version, but with the map_ptr problems I built 2.5.2 on that as well. However, version incompatibility was not the problem, as they persist after the

When using rsync 2.5.2 as daemon on a Solaris 2.5.1 box, I cannot copy data to rsync volumes with option 'use chroot'; I get the following messages on the client: pipe failed in do_recv rsync error: error in socket IO (code 10) at main.c(375) rsync: connection unexpectedly closed (69 bytes read so far) What seems to occur on the server is that socketpair(3) (not pipe(2)) is called,

I am trying to finalize the use of rsync for updatiung a new nfs server before we take the old one offline. I keep getting the following warning during the rsync process: Warning: unexpected rad size of 0 in map_ptr Any ideas where this comes from and how to make it go away? I am using rsync 2.5.2 on Solaris 8 to pull data from rsync 2.5.2 on Solaris 7. Bob roconnor@vectorpartners.com

Greetings! I'm experiencing these problems as described in this mail: ------- From: Thomas Quinot (thomas@melusine.cuivre.fr.eu.org) Subject: Rsync 2.5.5: FreeBSD mknod can't create FIFO's This is the only article in this thread View: Original Format Newsgroups: mailing.unix.rsync Date: 2002-06-24 06:05:25 PST The following patch

I have been trying to install 3.4p1 on a number of machines. Servers on ia64 Linux, i386 Linux and SPARC Solaris are all working like charms. On the other hand, I am having trouble at least with HPUX 11, DEC OSF 5.1 and Unixware: on all those systems, sshd bails out after authentication with an error in buffer_append_space. Here is the output of sshd -d on the UnixWare machine (uname -a:

Hi, I have compiled the new version 2.5.2 rsync in our servers, then ran rsync last night, there were some files not copied to destination server, both source and destination servers are running 2.5.2, I got the following error messages, can you please let me know what would be caused the errors? I copied back 2.3.2 version on both servers, and rsync went well. Thanks for the help, here is

On Wed, Jan 30, 2002 at 06:03:10PM -0500, Bill Nottingham wrote: > Dave Dykstra (dwd@bell-labs.com) said: > > I stumbled across the bug report > > http://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=58878 > > > > which shows that you made a bug fix to rsync on Sunday. What exactly did > > you do? > > Attached. It's the same thing as yours, I just

Rsync has begun failing to replicate a kerberos samba mount point. This mount point has worked previously, but recently an attempt to replicate the mount point returns; lseek failed in map_ptr rsync error: error in file IO (code 11) at fileio.c(228) rsync: writefd_unbuffered failed to write 4092 bytes: phase "unknown": Broken pipe rsync error: error in rsync protocol data stream (code

Greetings, I'd like to propose a new option to rsync, which causes it to read device files as if they were regular files. This includes pipes, character devices and block devices (I'm not sure about sockets). The main motivation is cases where you need to synchronize a large amount of data that is not available as regular files, as in the following scenarios: * Keep a copy of a block

https://bugzilla.samba.org/show_bug.cgi?id=1936 Summary: lseek failed in map_ptr Product: rsync Version: 2.6.3 Platform: x86 OS/Version: Windows XP Status: NEW Severity: normal Priority: P3 Component: core AssignedTo: wayned@samba.org ReportedBy: jitbose@yahoo.com QAContact:

On Jun 10, 2014 4:47 PM, "Thomas Quinot" <syslinux at thomas.cuivre.fr.eu.org> wrote: > * find proper fix for serial i/o (my crude hack handles > output, but not input; I now end up with a boot: prompt > but cannot enter anything). Is there a known correct way > of setting up pxelinux for serial-only I/O? Did you see the SERIAL directive? If this

On Jun 10, 2014 4:59 PM, "Thomas Quinot" <syslinux at thomas.cuivre.fr.eu.org> wrote: > > * Gene Cumm, 2014-06-10 : > > > Did you see the SERIAL directive? If this isn't enough, there may be bugs > > in the modules or the libraries they use. > > Yes, I'm aware of SERIAL, my config file has: > > serial 0 19200 0 > console 0 > >

* H. Peter Anvin, 2014-06-10 : > You probably want to test both pxelinux.0 and lpxelinux.0... if it is > sticking in pxe_init_isr you're using the latter. Correct. And indeed pxelinux.0 goes much further than lpxelinux.0! I have a few issues yet to fix: * Undef symbol FAIL: __syslinux_debug_enabled (I must have done something wrong while building) * find proper fix for

* Gene Cumm, 2014-06-10 : > Did you see the SERIAL directive? If this isn't enough, there may be bugs > in the modules or the libraries they use. Yes, I'm aware of SERIAL, my config file has: serial 0 19200 0 console 0 Thomas.

I've got a possibly silly question and I believe I have an answer, but I want to see if what I think is the answer is feasible. I've had to rebuild a mail server from scratch, upgrading from 4.6-STABLE to 4.8-STABLE in the process. The other mail server had crashed, with disk errors so sever it wouldn't fsck clean. I was able to get it together enough to pull my configuration files

Available now from samba.org and all mirrors. Please report bugs, compilation problems, etc. If there are no major issues I think I will put this out as 2.5.3 shortly, because it fixes a few serious issues. Thanks to everybody who contributed patches. rsync://samba.org/rsyncftp/preview/rsync-2.5.3pre1.tar.gz\* rsync 2.5.3 (not released yet) SECURITY FIXES: * Make sure that

Hi, When using rsync-3.0.2 through 3.0.5, I get this error on a large dataset syncing from machine-a to machine-b: $ /bin/rsync -aHSz /local/. machine-b:/local/. invalid len passed to map_ptr: -1737287498 rsync error: error in file IO (code 11) at fileio.c(188) [sender=3.0.5] This happens no matter which side initiates the connection, so this fails in the same way: $ /bin/rsync -aHSz

The following patch (adapted to rsync 2.5.5 from the one posted in Dec. 2000, http://lists.samba.org/pipermail/rsync/2000-December/003349.html) is necessary to prevent rsync from failing on creating FIFOs or UNIX sockets on FreeBSD. Any chance for it to be integrated in a future release of rsync? Thomas. diff -ur work/rsync-2.5.5/config.h.in work.patch/rsync-2.5.5/config.h.in ---

https://bugzilla.samba.org/show_bug.cgi?id=6293 Summary: rsync crashes when transferring files Product: rsync Version: 3.0.5 Platform: x86 OS/Version: Mac OS X Status: NEW Severity: normal Priority: P3 Component: core AssignedTo: wayned@samba.org ReportedBy: dirk.samba@miriup.de

Attached is a patch that makes window strides constant when files are walked with a constant block size. In these cases, it completely avoids all memmoves. In my simple local test of rsyncing 57MB of 10 local files, memmoved bytes went from 18MB to zero. I haven't tested this for a big variety of file cases. I think that this will always reduce the memmoves involved with walking a large