On 3/19/07, Craig Barratt <[EMAIL PROTECTED]> wrote:
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 s
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. Hopeful
On 3/18/07, Craig Barratt <[EMAIL PROTECTED]> wrote:
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
Charles writes:
> full backup started for directory /home/cswarts
> started full dump, share=/home/cswarts
> Running: /usr/bin/ssh -q -x -l rback -p 222 vps.deadeyedata.com sudo\
> /usr/bin/rsync --server --sender --numeric-ids --perms --owner --group -D
> --links --hard-links --times --block-size
I have recently installed BackupPC and am trying to get it configured.
Previously I was just using cron to schedule rsync over ssh.
Presently, I can backup my remote system with BackupPC just fine if I use
tar as the XferMethod. I would prefer to use rsync however.
I have on the server that is
