Hi Dean,
why wouldn't you just spawn the rdiff-backup program? otherwise you'd be dependent on the internal apis remaining stable... which doesn't seem like a good choice for your gui or for rdiff-backup development...
Well, I'm assuming that sooner or later rdiff-backup will have some kind of stable API that I can use. Also, the compiler (and python bytecode interpreter) will check that I'm using the correct API and give me a warning if not. Trying to parse the output of a process is a nightmare that I really don't want to get involved with (again).
progress meters kind of depend on knowing how much there is to be done, and rdiff-backup doesn't know that initially at least... because it starts transferring data even before it has scanned all the inodes needing backup.
Well, I guess I would have to change that :-)
but rdiff-backup could probably be easily mod'd to have an option to display how many inodes/bytes it had processed so far... just hook in where the file-statistics file is written...
Yeah. Cheers, Chris. -- _ ___ __ _ / __/ / ,__(_)_ | Chris Wilson <0000 at qwirx.com> - Cambs UK | / (_/ ,\/ _/ /_ \ | Security/C/C++/Java/Perl/SQL/HTML Developer | \ _/_/_/_//_/___/ | We are GNU-free your mind-and your software | _______________________________________________ rdiff-backup-users mailing list at [email protected] http://lists.nongnu.org/mailman/listinfo/rdiff-backup-users Wiki URL: http://rdiff-backup.solutionsfirst.com.au/index.php/RdiffBackupWiki
