On Thu, Jan 25, 2001 at 06:42:33PM +0100, [EMAIL PROTECTED] wrote:
>
> On 25.01.2001 17:59:53 Dave Dykstra wrote:
>
> > On Wed, Jan 24, 2001 at 01:21:14PM +0100, [EMAIL PROTECTED]
> wrote:
> > > Hi!
> > > When i try to sync the content of two directories i receive several
> > > different errors on recurrent attempts:
> > >
> > > rsync -al -e ssh --delete -v . user@xxxxx:/home/www/xxxxx/htdocs/
> > > Building file list
> > > . . . .
> > > . . . .
> > > . . . .
> > > . . . .
> > > . . . .
> > > . . . .
It's not literally printing out dots, is it? Is it printing varying lists
of successfully copied files?
> > > Write failed: Cannot allocate memory
> > > unexpected EOF in read_timeout
> > >
> > > or
> > >
> > > Write failed: Exec format error
> > > unexpected EOF in read_timeout
> > >
> > > or
> > > Write failed: Not a directory
> > > unexpected EOF in read_timeout
> > >
> > > Any hint?
> > >
> > > Georg
> > >
> > >
> >
> > Let us know the rsync version number and the operating systems on both
> ends.
> >
> > - Dave Dykstra
> Excuse me, here they are:
> rsync version 2.3.2 protocol version 21 on both systems
> Linux xxxx 2.2.17 #1 Sun Oct 29 14:58:37 CET 2000 i686 unknown
> Linux xxxx 2.4.0-test12 #1 Wed Dec 20 17:04:28 CET 2000 i686 unknown
> Both System have 512 Mb RAM and 512 Mb Swap
That is very bizarre because I see no "Write failed" string in the rsync
2.3.2 source code. The closed thing I see is "write failed on %s : %s".
Also, the message "Exec format error" corresponds to the system error
code ENOEXEC and that's not anything that can be returned from write(2).
Ah, I do see a "Write failed:" message in ssh 1.2.27 source. It seems
you have a problem with your ssh transport. Again, the ENOEXEC is
very strange because the message is printed right after a call to write().
- Dave Dykstra
