List Receiver wrote:
>
> I'm running rsyncd, and programming is probably way over my head. I glanced
> through the options that rsync can be called with, and the closest option I
> could see that *might* help would be the --sockopts parameter. The timeout
> is already 0 apparently, by default. I have no clue what would go with the
> sockopts parameter to make a connection more reliable, though. I'm assuming
> nothing would make it work, as the connection must actually be getting
> interrupted.
My guess is that something in the network is timing out idle connections
after some fairly short (for TCP) interval. If you set the keepalive
option on a connection, the endpoints will exchange packets periodically
even if there is no data to send so the network device should see some
traffic regularly. Try setting socket options = SO_KEEPALIVE in the
rsyncd config file or with --sockopts on the command line to see if it
helps.
--
Les Mikesell
[EMAIL PROTECTED]
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
BackupPC-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/backuppc-users
http://backuppc.sourceforge.net/
