Explain file attribute spooling a bit more.

diff --git a/docs/manual/spooling.tex b/docs/manual/spooling.tex
index 33cef0339e4a237a93f09fa6f0c30bb2be2a63ca..9d1e4a9aac947a4cbb35243d0490c0c3acad0911 100644 (file)
--- a/docs/manual/spooling.tex
+++ b/docs/manual/spooling.tex
@@ -114,11 +114,14 @@ will fail possibly in bizarre ways when the spool fills.
    spooling. In other words, it also  spools the catalog entries to disk. This is
    done so  that in case the job fails, there will be no catalog  entries
    pointing to non-existent tape backups. 
-\item Attribute despooling is done at the end of the job, as  a consequence,
-   after Bacula stops writing the data to  the tape, there may be a pause while
-   the attributes are sent  to the Directory and entered into the catalog before 
-   the job terminates. 
-\item Attribute spool files are always placed in the  working directory. 
+\item Attribute despooling occurs near the end of a job.  The Storage daemon
+   accumulates file attributes during the backup and  sends them to the
+   Director at the end of the job.  The Director then inserts the file
+   attributes into the catalog.  During this insertion, the tape drive may
+   be inactive.  When the file attribute insertion is completed, the job
+   terminates. 
+\item Attribute spool files are always placed in the  working directory of 
+   the Storage daemon.
 \item When Bacula begins despooling data spooled to disk, it  takes exclusive
    use of the tape. This has the major  advantage that in running multiple
    simultaneous jobs at  the same time, the blocks of several jobs will not be