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
> > > Pipe message to stderr). I thought maybe --blocking-io would avoid this
> > > issue, but it still happened when using --blocking-io.
> >
> > It would seem that the server process (forked off from the
> > daemon) is dying. Look in the rsyncd log file (may be
> > syslog) for clues.
>
> Yes, this does appear to be what is happening. I actually had tried
> looking at the daemon logs, but there didn't appear to be anything
> remotely interesting in it. This is the only line I see in the log:
>
> 2003/06/16 16:23:48 [17924] rsync to blah/blah/Blah/ from [EMAIL PROTECTED]
> (10.x.x.x)
>
> Is there any way to increase the verbosity for this? Adding -v's to the
> daemon process didn't appear to affect it. Oh well, I guess it's time to
> start debugging.
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.
--
________________________________________________________________
J.W. Schultz Pegasystems Technologies
email address: [EMAIL PROTECTED]
Remember Cernan and Schmitt
--
To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync
Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
