my problems continue
Sun, 03 Mar 2002 16:57:45 -0800
Content-Type: text/plain; charset=us-ascii
>>>>> "SV" == docv <email@example.com>
>>>>> wrote the following on Sun, 03 Mar 2002 17:26:46 -0600
SV> Finally I can give something back! I was able to get
SV> rdiff-backup to complete a session (yeah!!!).
Heh, congratulations. (I hope for other people this occurrence isn't
cause for shock and celebration...)
SV> I changed the 'EscapeChar ~' variable in /etc/ssh/ssh_config
SV> file to 'EscapeChar none'. I am guessing that somewhere in the
SV> transmitting of the data, it was receiving a '~.', which,
SV> according to the man page, is the code to end a session.
This is an interesting hypothesis, but the man page also says:
>> If no pseudo tty has been allocated, the session is transparent
>> and can be used to reliably transfer binary data. On most
>> systems, setting the escape character to ``none'' will also make
>> the session transparent even if a tty is used.
so I think ssh shouldn't be using a pseudo-tty anyway, and escaping
shouldn't be an issue. Other utilities, like rsync, seem to use ssh
without escaping problems.
SV> Now, is there an easy way to verify a complete backup?
It seems like there should be a simple shell command for this, but
there isn't one that I know of. I guess the problem is what it means
for two directories to be the same. For instance, I think mtime and
ownership differences shouldn't count as differences when it comes to
symlinks, but they should with regular files. Also if you are backing
up files you don't own, you probably aren't interested in the fact
that the backup has different ownership, etc.
Inside rdiff-backup there's a function RPath.cmp_recursive which
isn't used in normal operations but can compare directories
recursively. I use it on my end when testing, but its functionality
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: Exmh version 2.5 01/15/2001
-----END PGP SIGNATURE-----