Hi,

Peter Nankivell wrote on 2008-07-15 09:17:48 +1000 [Re: [BackupPC-users] 
aborted by signal=PIPE errors.]:
> [...]
> If it is all due to ssh and hardware it makes me worry about
> the resilience of ssh.  Surely its protocol should be able to
> retry on corrupted data?  I don't know...

actually, TCP should provide ssh with a reliable data stream. If ssh *sees*
corrupted data, then either

  1) the data has been tampered with or
  2) TCPs CRC failed to identify network data corruption.

While (2) is conceivable, it should *not* be happening on a regular basis (if
it is, something else is wrong). I would guess it to be so rare that ssh
ignores the possibility, since there is no way to distinguish between both
cases. In the case of tampering, retransmissions would not make much sense
("Hey, I noticed that! Be more subtle next time." :-).

> Another solution maybe to use "rsyncd".  This should avoid
> using ssh as the transport.  I haven't tried this yet.

Providing you really have a corrupted TCP data stream, that would mean
corrupted backups ... or an rsync protocol failure.

Regards,
Holger

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
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/