Implement TLS in gnome console and wx-console.

[bacula/bacula] / bacula / kernstodo

diff --git a/bacula/kernstodo b/bacula/kernstodo
index 6387dc40acfb3d619d7a8a7b1a292258c71acf26..94a37d23b135af9f1be9ef58b51a35df78041b03 100644 (file)
--- a/bacula/kernstodo
+++ b/bacula/kernstodo
@@ -1,5 +1,5 @@
                     Kern's ToDo List
-                     16 June 2005
+                     04 July 2005
 
 Major development:      
 Project                     Developer
@@ -23,9 +23,10 @@ Autochangers:
      all Volumes from other drives.  "update slots all-drives"?
 
 For 1.37:
+- update volume=xxx --- add status=Full
+- Remove old spool files on startup.
+- Exclude SD spool/working directory.
 - Finish TLS implementation.
-- Fix PostgreSQL GROUP BY problems in restore.
-- Fix PostgreSQL sql problems in bugs.
 - Refuse to prune last valid Full backup. Same goes for Catalog.
 - --without-openssl breaks at least on Solaris.
 - Python:
@@ -129,6 +130,45 @@ Maybe in 1.37:
 - Bug: if a job is manually scheduled to run later, it does not appear
   in any status report and cannot be cancelled.
 
+==== Keeping track of deleted files ====
+     My "trick" for keeping track of deletions is the following.
+     Assuming the user turns on this option, after all the files
+     have been backed up, but before the job has terminated, the
+     FD will make a pass through all the files and send their
+     names to the DIR (*exactly* the same as what a Verify job
+     currently does).  This will probably be done at the same
+     time the files are being sent to the SD avoiding a second
+     pass.  The DIR will then compare that to what is stored in
+     the catalog.  Any files in the catalog but not in what the
+     FD sent will receive a catalog File entry that indicates
+     that at that point in time the file was deleted.
+
+     During a restore, any file initially picked up by some
+     backup (Full, ...) then subsequently having a File entry
+     marked "delete" will be removed from the tree, so will not
+     be restored.  If a file with the same name is later OK it
+     will be inserted in the tree -- this already happens.  All
+     will be consistent except for possible changes during the
+     running of the FD.
+
+     Since I'm on the subject, some of you may be wondering what
+     the utility of the in memory tree is if you are going to
+     restore everything (at least it comes up from time to time
+     on the list).  Well, it is still *very* useful because it
+     allows only the last item found for a particular filename
+     (full path) to be entered into the tree, and thus if a file
+     is backed up 10 times, only the last copy will be restored.
+     I recently (last Friday) restored a complete directory, and
+     the Full and all the Differential and Incremental backups
+     spanned 3 Volumes.  The first Volume was not even mounted
+     because all the files had been updated and hence backed up
+     since the Full backup was made.  In this case, the tree
+     saved me a *lot* of time.
+
+     Make sure this information is stored on the tape too so
+     that it can be restored directly from the tape.
+=====
+
 Regression tests:
 - Add Pool/Storage override regression test.
 - Add delete JobId to regression.
@@ -1297,4 +1337,13 @@ Block Position: 0
 - Make sure that Python has access to Client address/port so that
   it can check if Clients are alive.
 - Review all items in "restore".
+- Fix PostgreSQL GROUP BY problems in restore.
+- Fix PostgreSQL sql problems in bugs.
+- After rename
+  04-Jul 13:01 MainSD: Rufus.2005-07-04_01.05.02 Warning: Director wanted Volume 
+     "DLT-13Feb04".
+  Current Volume "DLT-04Jul05" not acceptable because:
+  1997 Volume "DLT-13Feb04" not in catalog.
+  04-Jul 13:01 MainSD: Please mount Volume "DLT-04Jul05" on Storage Device 
+     "HP DLT 80" (/dev/nst0) for Job Rufus.2005-07-04_01.05.02