[Bacula-commits] git: Bacula Documentation branch, master, updated. 0a01dc6f6b3f32854bbf4fd4d087381c30974751

[Kern S. <ke...@us...>]

This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "Bacula Documentation".

The branch, master has been updated
       via  0a01dc6f6b3f32854bbf4fd4d087381c30974751 (commit)
      from  2b7b57b96dc6d53138e1f14e7e7fdf864f714551 (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -----------------------------------------------------------------
commit 0a01dc6f6b3f32854bbf4fd4d087381c30974751
Author: Kern Sibbald <ke...@si...>
Date:   Mon May 24 17:18:06 2010 +0200

    Tweak

-----------------------------------------------------------------------

Summary of changes:
diff --git a/docs/manuals/en/main/state.tex b/docs/manuals/en/main/state.tex
index 547be05..3312e2f 100644
--- a/docs/manuals/en/main/state.tex
+++ b/docs/manuals/en/main/state.tex
@@ -245,6 +245,8 @@ In other words, what is and what is not currently implemented and functional.
   or by explicitly updating the date/time stamp on all moved files.
 \item In older versions of Bacula ($<=$ 3.0.x), if you have over 4 billion file
   entries stored in your database, the database FileId is likely to overflow.
+  This limitation does not apply to current Bacula versions.
 \item In non \textsl{Accurate} mode, files deleted after a Full save will be
   included in a restoration. This is typical for most similar backup programs.
+  To avoid this, use Accurate mode backup.
 \end{itemize}


hooks/post-receive
-- 
Bacula Documentation