> -----Original Message----- > From: Les Mikesell [mailto:[EMAIL PROTECTED] > Sent: Monday, October 22, 2007 8:40 AM > To: List Receiver > Cc: Carl Wilhelm Soderstrom; [email protected] > Subject: Re: [BackupPC-users] Rsync fulls complete, but incrementals > don't > > List Receiver wrote: > > > > That doesn't help me here, as some of my WAN hosts are unpingable. > I've replaced the ping utility with echo. As well, even if I was > pinging the hosts prior to starting the backup, this would only adjust > whether or not the backup started, not whether or not it would > complete. The backup is always starting, and as far as I know, always > getting a transfer ID. It just never completes an incremental. > > > > I think what you need, if you can't fix the network, is to turn on > keepalives on the socket for the connection. If you are running over > ssh, adding -o TCPKeepAlive to the ssh command line should do it. If > you are using rsyncd at the other end you'd probably have to modify the > perl code that talks directly to it. > > -- > Les Mikesell > [EMAIL PROTECTED]
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. ------------------------------------------------------------------------- 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/
