Just for the record, the patch to token.c for the -z bug that was
discovered by Yasuoka Masahiko and patched by him and Wayne Davison
has fixed the problem that I reported here:
http://www.mail-archive.com/[EMAIL PROTECTED]/msg07289.html
Thanks guys, this bug has been biting me for the past 6
On Wed, Jun 18, 2003 at 10:38:54AM -0400, Andrew J. Schorr wrote:
> On Tue, Jun 17, 2003 at 06:35:50AM -0700, jw schultz wrote:
> >
> > You could try turning on transfer logging i suppose. If you
> > haven't already done so you might want to use the "log file"
> > option in case chroot is getting
On Tue, Jun 17, 2003 at 06:35:50AM -0700, jw schultz wrote:
>
> You could try turning on transfer logging i suppose. If you
> haven't already done so you might want to use the "log file"
> option in case chroot is getting in the way. Beyond this i
> have no suggestions; i dont use rsyncd.
I may
On Tue, Jun 17, 2003 at 09:10:38AM -0500, Nathaniel Case wrote:
> On Mon, 16 Jun 2003 at 16:24:25 -0700, jw schultz wrote:
> >
> > > After looking at io.c, it seems like the problem (rather, the symptom)
> > > for
> > > this error message is a failed write() call (which explains the Broken
> > > Pi
On Mon, 16 Jun 2003 at 16:24:25 -0700, jw schultz wrote:
>
> > After looking at io.c, it seems like the problem (rather, the symptom)
> > for
> > this error message is a failed write() call (which explains the Broken
> > Pipe message to stderr). I thought maybe --blocking-io would avoid this
> > i
On Mon, Jun 16, 2003 at 11:53:04AM -0500, Nate Case wrote:
> I'm experiencing some unexpected behavior with rsync v2.5.6. After
> looking around it seems like several people have experienced similar
> problems in the past, but those appear to be old bugs that are solved now.
> Also doesn't appear
