On 04/12/15 14:51, Carl Wilhelm Soderstrom wrote:
> Don't try to do rsync+ssh on Windows, just use rsyncd. Maybe someone else
> has gotten rsync+ssh to work on Windows but AFAIK the conventional wisdom is
> that it doesn't work. (Someone probably knows why, but that someone is not
> me).
Well,
On 05/12/15 16:59, Les Mikesell wrote:
>> Well, as I mentioned, rsyncd didn't work either. That's the reason I
>> switched to ssh+rsync in the first place.
>>
>> I can re-run it using rsync and give you that info too.
> Your situation sounds like what can happen if your vpn or a NAT
> gateway
On Sat, Dec 5, 2015 at 9:28 AM, David Raison wrote:
>
>
> On 04/12/15 14:51, Carl Wilhelm Soderstrom wrote:
>> Don't try to do rsync+ssh on Windows, just use rsyncd. Maybe someone else
>> has gotten rsync+ssh to work on Windows but AFAIK the conventional wisdom is
>> that
On Sat, Dec 5, 2015 at 10:37 AM, David Raison wrote:
>
> Well I did have ServerAliveInterval set. And as I mentioned, a parallel
> ssh session was still up, even when backuppc/rsync reported a timeout/EOF:
Yes, that is the problem you really need to solve. Why is your