> Something is closing the session between the client and
> server. The last time this was happening it was a firewall.
> This could also be caused by an error in the TCP protocol
> stack.
>
> > ... but I got suspicious and changed out the NIC on the client machine.
>
> Are you saying that fixed i
On Sun, Sep 07, 2003 at 11:32:24PM -0400, Jim Salter wrote:
> > What you describe is that the sender is dying but you don't
> > get a message from it as to why. Start by looking in the
> > rsyncd log file. If that doesn't yield an informative
> > message try pushing the transfer (run it on the ot
> What you describe is that the sender is dying but you don't
> get a message from it as to why. Start by looking in the
> rsyncd log file. If that doesn't yield an informative
> message try pushing the transfer (run it on the other system
> with the args switched) then you should see an error
>
On Sun, Sep 07, 2003 at 09:01:37PM -0400, Jim Salter wrote:
> Hello all -
>
> I am running rsync 2.5.6 on two FreeBSD 5.0 machines. I have experimented
> with running rsync using ssh, with command lines like the following:
>
> rsync -rv --progress [EMAIL PROTECTED]:/usr/share/smbshare
> /us
Hello all -
I am running rsync 2.5.6 on two FreeBSD 5.0 machines. I have experimented
with running rsync using ssh, with command lines like the following:
rsync -rv --progress [EMAIL PROTECTED]:/usr/share/smbshare
/usr/home/jimbo
And also with running rsync as a daemon on the master server
