two stupid questions
Ben Escoto
bescoto@stanford.edu
Wed, 01 May 2002 09:46:02 -0700
--==_Exmh_1801642468P
Content-Type: text/plain; charset=us-ascii
>>>>> "DG" == David Garamond <davegaramond@icqmail.com>
>>>>> wrote the following on Wed, 01 May 2002 19:05:19 +0700
DG> my two stupid questions:
DG> 1) what if i have a subdirectory named rdiff-backup-data/ in the
DG> first subdirectory level? currently rdiff-backup totally ignores
DG> it. can i move the rdiff-backup-data/ directory outside the
DG> destination directory?
No, I do not think there is any obvious way of doing this currently
(maybe some NFS trick?). Hmm, it might be nice to have a syntax like:
rdiff-backup --data-dir user1@host1::/rdiff-backup-data \
user2@host2::/source \
user3@host3::/backup
but no one has ever asked about something like that before.
DG> 2) can i speed up backup-rdiff invocation? since python has to
DG> compile thousands of lines per invocation, this took almost two
DG> seconds. a little bit annoying. my quick hack is like this:
DG> rename rdiff-backup to rdiff_backup.py and create a wrapper
DG> python script rdiff-backup:
...
DG> perhaps another step is to rearrange rdiff_backup to become two
DG> parts? a library that can be used programatically from other
DG> python code, and the rdiff-backup executable that mainly
DG> consists of argument parsing?
On my machine it takes python about 0.5 seconds to compile
rdiff-backup, so I didn't mind the delay (also I only use it for
nightly backups, so 30 minutes or 30 minutes + 0.4 seconds doesn't
make much difference). But it is possible to speed things up as you
have shown. The only tradeoff is that rdiff-backup would be harder to
install because the module part would have to be put in the right
directory, which seems to change depending on the version of python.
So they aren't stupid questions at all. I would be interested to
know how many people would find rdiff-backup more useful with 1 and/or
2 above.
--
Ben Escoto
--==_Exmh_1801642468P
Content-Type: application/pgp-signature
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: Exmh version 2.5 01/15/2001
iD4DBQE80BvG+owuOvknOnURAi7JAJ0ZQW876REw9/mBmuTiYTUm8WIYUgCVHi81
iycPJbQ2xhzUf5khLHWdsA==
=BqbP
-----END PGP SIGNATURE-----
--==_Exmh_1801642468P--