BackupPC-users

Re: [BackupPC-users] BackupPC fails with aborted by signal=PIPE, Can't write to socket

2017-01-24 15:04:20
Subject: Re: [BackupPC-users] BackupPC fails with aborted by signal=PIPE, Can't write to socket
From: John Spitzer <johned9999 AT comcast DOT net>
To: s_peter AT swissonline DOT ch, "General list for user discussion, questions and support" <backuppc-users AT lists.sourceforge DOT net>
Date: Tue, 24 Jan 2017 12:03:43 -0800
Stefan, Les,

Thanks you for your excellent suggestions. I have solved the problem by 
increasing the config value: timeout=2400 in the rsyncd.conf file.

I appreciate the time you took to help.

John
On 01/20/2017 12:18 PM, Stefan Peter wrote:
> On 20.01.2017 09:13, Stefan Peter wrote:
>> If you use the rsync method, make sure your
>> RsyncClientCmd does not use the --timeout parameter or at least sets a
>> reasonably high paramter value.
> As an afterthought, I suppose the BackupPC parameter
> $Conf{ClientTimeout} from the clients Backup Settings may be used to set
> the rsync timeout. But I did not verify this and the BackupPC help does
> not explicitly mention rsync.
>
> With kind regards
>
> Stefan Peter
>

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
_______________________________________________
BackupPC-users mailing list
BackupPC-users AT lists.sourceforge DOT net
List:    https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki:    http://backuppc.wiki.sourceforge.net
Project: http://backuppc.sourceforge.net/