Craig Barratt writes: > > Got checksumSeed 0x69647473 > > Read EOF: > > The checksumSeed doesn't look right. If you don't specify it on > the command line, it should default to unix time(). > > In your case it comprises the four ascii characters "idts". That > isn't coming from rsync. Hopefully that is a clue for you.
I forgot to mention the checksum seed is sent little-endian, so the actual bytes are "stdi". This is the first part of an error message, like "stdin: not a tty". The fact that this appears after the rsync protocol version is correctly sent suggests that a backgrounded process (stty?) is writing the characters after rsync starts. Craig ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ BackupPC-users mailing list BackupPC-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/backuppc-users http://backuppc.sourceforge.net/
