From: Kern Sibbald Date: Thu, 21 Sep 2006 22:15:32 +0000 (+0000) Subject: Update X-Git-Tag: Release-2.0.0~424 X-Git-Url: https://git.sur5r.net/?a=commitdiff_plain;h=05cae6fb8e9366ea1f5bfa42d6ed810c75a12319;p=bacula%2Fdocs Update --- diff --git a/docs/manual/catmaintenance.tex b/docs/manual/catmaintenance.tex index b23dbc59..87f86daf 100644 --- a/docs/manual/catmaintenance.tex +++ b/docs/manual/catmaintenance.tex @@ -104,7 +104,6 @@ time you run a Job. \end{description} \label{CompactingMySQL} - \subsection*{Compacting Your MySQL Database} \index[general]{Database!Compacting Your MySQL } \index[general]{Compacting Your MySQL Database } @@ -204,8 +203,8 @@ ALTER TABLE File MAX_ROWS=281474976710656; \end{verbatim} \normalsize -Alternatively you can modify your /etc/my.conf file and in the -[mysqld] section set: +Alternatively you can modify your /etc/my.conf file before creating the +Bacula tables, and in the [mysqld] section set: \footnotesize \begin{verbatim} @@ -213,8 +212,11 @@ set-variable = myisam_data_pointer_size=6 \end{verbatim} \normalsize -The above row and point size changes should already be the default on MySQL -version 5.x, so these changes should only be necessary on MySQL 4.x +The above myisam data pointer size must be made before you create your +Bacula tables or it will have no effect. + +The row and pointer size changes should already be the default on MySQL +version 5.x, so making these changes should only be necessary on MySQL 4.x depending on the size of your catalog database. @@ -512,7 +514,7 @@ The basic sequence of events to make this work correctly is as follows: \item You use {\bf RunBeforeJob} to create the ASCII backup file and {\bf RunAfterJob} to clean up - \end{itemize} +\end{itemize} Assuming that you start all your nightly backup jobs at 1:05 am (and that they run one after another), you can do the catalog backup with the following diff --git a/docs/manual/security.tex b/docs/manual/security.tex index e1dbd8af..726ab8e2 100644 --- a/docs/manual/security.tex +++ b/docs/manual/security.tex @@ -29,9 +29,9 @@ and/or using tcp wrappers ({\bf etc/hosts.allow}). \item By default, all data that is sent across the network is unencrypted. However, Bacula does support TLS (transport layer security) and can - encrypt transmitted data. Please read \ilink{Data Encryption}{DataEncryption} + encrypt transmitted data. Please read the + \ilink{TLS (SSL) Communications Encryption}{CommEncryption} section of this manual. - built-in. \item You should ensure that the Bacula working directories are readable and writable only by the Bacula daemons. \item If you are using {\bf MySQL} it is not necessary for it to run with diff --git a/docs/manual/version.tex b/docs/manual/version.tex index a643c871..aba939eb 100644 --- a/docs/manual/version.tex +++ b/docs/manual/version.tex @@ -1 +1 @@ -1.39.23 (16 September 2006) +1.39.23 (20 September 2006)