David Steele f93c6caec2 Backup/restore copy will be run in the main process when thread-max=1. I've resisted this change because it adds complexity, but I have to accept that threads are not stable on all platforms. Or maybe any platform.

2015-02-28 10:23:33 -05:00

..

Backup.pm

Backup/restore copy will be run in the main process when thread-max=1. I've resisted this change because it adds complexity, but I have to accept that threads are not stable on all platforms. Or maybe any platform.

2015-02-28 10:23:33 -05:00

Config.pm

Fixed restore::thread-max

2015-01-31 15:37:59 -05:00

Db.pm

Implemented timestamp last modified to record the time of the last modified file in the backup. Also added timestamp-db-start and timestamp-db-stop to for more info. timestamp-db-start can be used for PITR.

2015-01-03 16:49:26 -05:00

Exception.pm

Timeline unit tests are working.

2015-01-31 13:48:09 -05:00

File.pm

Looks like all unit tests pass - now for a long test run to see if that is really true. And to see if the old lockup is gone.

2015-02-27 23:31:39 -05:00

Manifest.pm

Fixes to restore compare unit tests.

2015-02-02 18:33:11 -05:00

Remote.pm

Looks like all unit tests pass - now for a long test run to see if that is really true. And to see if the old lockup is gone.

2015-02-27 23:31:39 -05:00

Restore.pm

Backup/restore copy will be run in the main process when thread-max=1. I've resisted this change because it adds complexity, but I have to accept that threads are not stable on all platforms. Or maybe any platform.

2015-02-28 10:23:33 -05:00

ThreadGroup.pm

Working on removing threads from instream compress/decompression.

2015-02-26 09:22:05 -05:00

Utility.pm

Fixed wait_for_file() so that it will not error if the path does not yet exist.

2015-01-28 00:26:20 -05:00