\pdfminorversion=4
-\def\version{7.4.1}
+\def\version{7.4.2}
%%
\index[general]{Installing and Configuring MySQL -- Phase I }
\index[general]{Phase I!Installing and Configuring MySQL -- }
+If you have installed MySQL from a package (.deb, .rpm, ...) or
+already installed it from source, please skip to the next section.
+
If you use the ./configure \verb:--:with-mysql=mysql-directory statement for
configuring {\bf Bacula}, you will need MySQL version 4.1 or later installed
in the {\bf mysql-directory}. If you are using one of the new modes such as
\footnotesize
\begin{verbatim}
-mysql-directory/bin/mysql -u root mysql
+<mysql-directory>/bin/mysql -u root mysql
select * from user;
\end{verbatim}
\normalsize
+Newer versions of MySQL (e.g. 5.7) do not automatically create a user
+when granting permissions with the {\bf grant\_mysql\_privileges}, and
+so the script may fail. In that case, you will want to do something
+similar to the following:
+
+\footnotesize
+\begin{verbatim}
+su
+(enter root password)
+<mysql-directory>/bin/mysql mysql
+create user bacula identified by '<password>';
+\end{verbatim}
+\normalsize
+
+then re-run the script.
+
\section{Re-initializing the Catalog Database}
\index[general]{Database!Re-initializing the Catalog }
\index[general]{Re-initializing the Catalog Database }
\subsection{SSL Connections to MySQL}
There are five new Directives for the Catalog resource in the
-\bf{bacula-dir.conf} file that you can use to encrypt the
+{\bf bacula-dir.conf} file that you can use to encrypt the
communications between Bacula and MySQL for additional
security.
that Full jobs.
\subsection{New List Volumes Output}
-The \bf{list} and \bf{llist} commands have been modified so that when
-listing Volumes a new pseudo field \bf{expiresin} will be printed. This
+The {\bf list} and {\bf llist} commands have been modified so that when
+listing Volumes a new pseudo field {\bf expiresin} will be printed. This
field is the number of seconds in which the retention period will expire.
If the retention period has already expired the value will be zero. Any
non-zero value means that the retention period is still in effect.
\index[general]{Installing and Configuring PostgreSQL }
\index[general]{Upgrading}
-If you are considering using PostreSQL, you should be aware
-of their philosophy of upgrades, which could be
-destabilizing for a production shop. Basically at every major version
-upgrade, you are required to dump your database in an ASCII format,
-do the upgrade, and then reload your database (or databases). This is
-because they frequently update the "data format" from version to
-version, and they supply no tools to automatically do the conversion.
-If you forget to do the ASCII dump, your database may become totally
-useless because none of the new tools can access it due to the format
-change, and the PostgreSQL server will not be able to start.
+If you have installed PostgreSQL from a package (.deb, .rpm, ...) or
+already installed it from source, please skip to the next section.
If you are building PostgreSQL from source, please be sure to add
the {\bf \verb:--:enable-thread-safety} option when doing the ./configure
or you will have to create one for it, but it does not need to
create new users.
+ In newer versions of PostgreSQL, it will not automatically ask
+ if the user {\bf bacula} should be able to create databases or
+ create new users. In that case, you may need to add one of the
+ many command line options that the program {\bf creatuser} has.
+ Please see the PostgreSQL documentation that corresponds to the
+ version you are using.
+
\item ./create\_bacula\_database
This script creates the PostgreSQL {\bf bacula} database.
-7.4.1 (02 May 2016)
+7.4.2 (06 June 2016)
cwd=`pwd`
lang=$1
src=$cwd/manuals/${lang}/pdf-and-html
-ver=7.4.0
+ver=7.4.1
repo=release
echo "ver=${ver}"