problem with 2.4.7pre4
Jeremy Hansen
jeremy at xxedgexx.com
Fri Nov 30 11:50:56 EST 2001
Actually, I did it this time without stunnel and got the same results:
Nov 29 16:49:49 rio rsyncd[24007]: transfer interrupted (code 20) at
rsync.c(229)
It's literally right at the end of the transfer. Somewhere in renaming
the temp file or something??
-jeremy
On Thu, 29 Nov 2001, Jeremy Hansen wrote:
>
>
> So...it seems I did receive an error from stunnel. So now do I have to go
> off to the stunnel list :-)
>
> Nov 29 16:26:04 rio stunnel[20970]: SSL_write (ERROR_SYSCALL): Broken pipe
> (32)
> Nov 29 16:26:04 rio stunnel[20970]: Connection reset: 53424205 bytes sent
> to SSL, 104 bytes sent to socket
> Nov 29 16:26:04 rio rsyncd[20971]: transfer interrupted (code 20) at
> rsync.c(229)
>
> Thanks
> -jeremy
>
> On Thu, 29 Nov 2001, Jeremy Hansen wrote:
>
> > On Fri, 30 Nov 2001, Martin Pool wrote:
> >
> > > On 29 Nov 2001, Jeremy Hansen <jeremy at xxedgexx.com> wrote:
> > >
> > > > rsync -avz --progress rsync://localhost/apache_logs/access_log .
> > >
> > > tridge just reminded me that -a does *not* detect hardlinks. You need
> > > -H too.
> >
> > Hmm, there are no hard links involved here. I think you're confusing me
> > with another poster.
> >
> > I'll do the trace on stunnel.
> >
> > Thanks
> > -jeremy
> >
> > > A documentation bug implied that -a was enough. I've just fixed it.
> > >
> > >
> >
> >
>
>
--
The trouble with being poor is that it takes up all your time.
More information about the rsync
mailing list