Comment 6 for bug 191681
Revision history for this message
| Andrew Stromme (astromme) wrote Re: If an external drive is used for backups, Timevault will write backups if the drive is not present | #6 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
1b1ed1a
(Get the code!)
At the moment (revision 44 of timevault-external) timevault sets a uuid for the drive (if it's other than root) that stores the backups. Then, upon each configuration reload (Meaning at application startup or after any conf change) it checks for a valid backup drive before doing anything. If the drive is not present, it shows an error status in timevault-notifier and prompts the user to plug in the backup drive.
I still haven't figured how to make it continue to check for the backup drive (or get automatically notified when it gets plugged in). HAL will probably do this for me. Also, once the drive has been plugged in and timevault starts using it it will not give it up until the process is stopped. To change this behavior, I think I have to dig deeper into how timevault works and how it stores information on the drive. I'm afraid that it won't be easy. Although, there might be a way to set up a 'disable' event where it releases control of the drive.