Sorry, it appears I was chasing my tail. After
a day of configuration, testing, and looking through
code to understand it, I was simply editing out of my conciousness
a read only error on the client side. However, it may be a good idea to put
some of those errors on the server side, at least on a command line
flagged basis. I'll try to take a look through the code...
Thanks,
Alex Peyser
-----Original Message-----
From: Alex Peyser [mailto:[EMAIL PROTECTED]]
Sent: Thursday, March 15, 2001 7:24 PM
To: '[EMAIL PROTECTED]'
Subject: Peer reset
I've got rsync 2.4.6 protocol version 24 running as an inetd server under
solaris 2.7.
I've got set the modules set up, authentication goes ok. Then I get a
reverse dns warning... which is fine
with me, the security isn't running through rsync anyhow (and in the rsync
source code that appears to
be a warning that doesn't cause a failure). Then my client get a peer reset
error.
That happens whether or not I'm coming in over a wan, lan, or through
localhost.
I get no error in syslog on the server error, just the read error in
read_timeout on the client side.
Anyone have any idea ?
Thanks,
Alex Peyser
