David Steele d2602a5c07 Tracking down a lockup in the restore threads. It doesn't happen in backup - they are the same except that restore uses the ThreadGroup object. I'm beginning to think that threads and objects don't play together very nicely. Objects in threads seems OK, but threads in objects, not so much.		2015-02-03 20:33:33 -05:00
..
Backup.pm	Tracking down a lockup in the restore threads. It doesn't happen in backup - they are the same except that restore uses the ThreadGroup object. I'm beginning to think that threads and objects don't play together very nicely. Objects in threads seems OK, but threads in objects, not so much.	2015-02-03 20:33: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	Revert "Abortive attempt at cleaning up some thread issues - I realized the issue is in mixing threads and objects too liberally. Trying another approach but want to keep this code for historical and reference purposes."	2015-01-30 18:58:49 -05:00
Manifest.pm	Fixes to restore compare unit tests.	2015-02-02 18:33:11 -05:00
ProcessAsync.pm	In the end it was a single non-undefed reference holding up the show. The Backup file should be split into Archive, Backup, Expire, and made into objects. That would cut down on this kind of nastiness.	2015-01-30 20:16:21 -05:00
Remote.pm	Revert "Abortive attempt at cleaning up some thread issues - I realized the issue is in mixing threads and objects too liberally. Trying another approach but want to keep this code for historical and reference purposes."	2015-01-30 18:58:49 -05:00
Restore.pm	Tracking down a lockup in the restore threads. It doesn't happen in backup - they are the same except that restore uses the ThreadGroup object. I'm beginning to think that threads and objects don't play together very nicely. Objects in threads seems OK, but threads in objects, not so much.	2015-02-03 20:33:33 -05:00
ThreadGroup.pm	Revert "Abortive attempt at cleaning up some thread issues - I realized the issue is in mixing threads and objects too liberally. Trying another approach but want to keep this code for historical and reference purposes."	2015-01-30 18:58:49 -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