Rdiff-backup

Latest version: v2.4.0

Safety actively analyzes 638730 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 15 of 19

0.6.0

Fixed some assorted manual "bugs".

Fixed endless loop bug in certain error recovery situation reported by Nick Duffek, and slightly changed around some other error correction code.

Switching to new version numbering system: versions x.2n+1.x are unstable, versions x.2n.x are supposed to be more stable.

0.5.4

Fixed bug present since 0.5.0 wherein rdiff-backup would make snapshots instead of diffs when regular files change.

May have fixed race condition involving rdiff execution.

0.5.3

It turns out the previous version broke device handling.
Sorry about that..

0.5.2

Fixed bugs which made rdiff-backup try to preserve mod times when it wasn't necessary, and exit instead of warning when it wasn't being run as root and found a file it didn't own.
(Reported by Alberto Accomazzi.)

Added some more error checking;
maybe this will fix a bug reported by John Goerzen wherein rdiff-backup can crash if file is deleted while rdiff-backup is processing it.

Changed locations of some of the temp files;
filenames will be determined by the tempfile module.

0.5.1

When establishing a connection, print a warning if the server version is different from the client version.

When find rdiff error value 256, tell user that it is probably because rdiff couldn't be found in the path.

Fixed a serious bug that can apparently cause a remote backups to fail (reported by John Goerzen).

May have fixed a bug that causes recovery from certain errors to fail.

0.5.0

Now every so often (default is 20 seconds, the --checkpoint-interval option controls it) rdiff-backup checkpoints by dumping its state to temporary files in the rdiff-backup-data directory.
If rdiff-backup is rerun with the same destination directory, it can either try to resume the previous backup or at least clean things up so the archive is consistent and accurate.

Added new options --resume, --no-resume, and --resume-interval, which control when rdiff-backup tries to resume a previous failed backup.

Fixed a bug with the --exclude-device-files option which caused the option to be ignored when the source directory was remote.

By default, if rdiff-backup encounters a certain kind of IOError (currently types 26 and 5) while trying to access a file, it logs the error, skips the file, and tries to continue.

If settings requiring an integer argument (like -v or --checkpoint-interval) are given a bad (non-integer) argument, fail with better explanation.

Fixed annoying logging bug.
Now no matter which computer a logging message originates on, it should be routed to the process which is writing to the logging file, and written correctly.
However, logging messages about network traffic will not be routed, as this will generate more traffic and lead to an infinite regress.

When calling rdiff, uses popen2.Popen3 and os.spawnvp instead of os.popen and os.system.
This should make rdiff-backup more secure.
Thanks to Jamie Heilman for the suggestion.

Instead of calling the external shell command 'stat', rdiff-backup uses os.lstat().st_rdev to determine a device file's major and minor numbers.
The new method should be more portable.
Thanks to Jamie Heilman for the suggestion.

All the file operations were examined and tweaked to try to minimize/eliminate the chance of leaving the backup directory in an inconsistent state.

Upon catchable kinds of errors, try to checkpoint before exiting so later rdiff-backup processes have more information to work with.

At the suggestion of Jason Piterak, added a --windows-time-format option so rdiff-backup will (perhaps) work under MS windows NT.

Page 15 of 19

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.