Timothy J Massey wrote at about 12:05:02 -0400 on Thursday, May 31, 2012:
> Pascal Mosimann wrote on 05/31/2012
> 11:12:54 AM:
>
> > > Why does BackupPC run the parity command if I've told it not to by
> > passing
> > > it a 0? And how do I return to the 3.1 behavior? According to the
Pascal Mosimann wrote on 05/31/2012
11:12:54 AM:
> > Why does BackupPC run the parity command if I've told it not to by
> passing
> > it a 0? And how do I return to the 3.1 behavior? According to the
> > documentation, setting it to 0 should disable it, not cause it to run
> with
> > a
> Why does BackupPC run the parity command if I've told it not to by
passing
> it a 0? And how do I return to the 3.1 behavior? According to the
> documentation, setting it to 0 should disable it, not cause it to run
with
> a parameter of 0... And if for some reason we would *want* the
pa
On Wed, 2012-05-30 at 14:05 -0400, Neal Becker wrote:
> Using rsync (via ssh), default is aes encryption, which is expensive.
>
> I wanted to try setting
>
> Host * Ciphers arcfour,blowfish-cbc
>
> I put that in user backuppc .ssh/config, but that didn't seem to work
> (according
> to the outp
