added notes about MariaDB, cleanup

manuals/en/main/bareos-manual-main-reference.tex

@@ -213,7 +213,7 @@ \part{Appendix}
 
 \chapter{Operating Systems}
 \label{SupportedOSes}
-\index[general]{Systems!Supported Operating}
+\index[general]{Systems!Supported Operating Systems}
 \index[general]{Support!Operating Systems}
 
     \input{supportedoses}

manuals/en/main/catmaintenance.tex

@@ -12,12 +12,16 @@ \section{Catalog Database}
 Different database backends are supported:
 \begin{itemize}
     \item PostgreSQL
-    \item MySQL
+    \item MySQL/MariaDB
     \item Sqlite (only for testing)
 \end{itemize}
 
 What database will be used, can be configured in \file{/etc/bareos/bareos-dir.conf}, see the \nameref{DirectorResourceCatalog}.
 
+As MariaDB is a fork of MySQL, we use MySQL as synonym for MariaDB.
+We test our packages against the prefered MySQL fork that a distribution provides.
+\index[general]{MariaDB|see{MySQL}}
+
 The database often runs on the same server as the Bareos Director.
 However, it is also possible to run it on a different system.
 This might require some more manual configuration.
@@ -728,9 +732,11 @@ \subsubsection{Job statistics}
 
 \section{PostgreSQL}
 
+\index[general]{Database!PostgreSQL}
+\index[general]{PostgreSQL}
+
 \subsection{Compacting Your PostgreSQL Database}
-\index[general]{Database!Compacting Your PostgreSQL}
-\index[general]{Compacting Your PostgreSQL Database}
+\index[general]{Database!PostgreSQL!Compacting}
 \label{CompactingPostgres}
 
 Over time, as noted above, your database will tend to grow until Bareos starts
@@ -758,8 +764,8 @@ \subsection{Compacting Your PostgreSQL Database}
 scratch producing a compacted result, so below, we show you how you can do
 this for PostgreSQL.
 
-For a {\bf PostgreSQL} database, you could write the Bareos database as an
-ASCII file (\texttt{bareos.sql}) then reload it by doing the following:
+For a PostgreSQL database, you could write the Bareos database as an
+ASCII file (\file{bareos.sql}) then reload it by doing the following:
 
 \begin{commands}{}
 pg_dump -c bareos > bareos.sql
@@ -768,9 +774,9 @@ \subsection{Compacting Your PostgreSQL Database}
 \end{commands}
 
 Depending on the size of your database, this will take more or less time and a
-fair amount of disk space. For example, you can {\bf cd} to the location of
-the Bareos database (typically \texttt{/var/lib/pgsql/data} or possible
-\texttt{/usr/local/pgsql/data}) and check the size.
+fair amount of disk space. For example, you can \command{cd} to the location of
+the Bareos database (typically \directory{/var/lib/pgsql/data} or possible
+\directory{/usr/local/pgsql/data}) and check the size.
 
 Except from special cases PostgreSQL does not
 need to be dumped/restored to keep the database efficient.  A normal
@@ -940,12 +946,13 @@ \subsection{Repairing Your PostgreSQL Database}
 
 
 
-\section{MySQL}
+\section{MySQL/MariaDB}
 
+\index[general]{Database!MySQL}
+\index[general]{MySQL}
 
 \subsection{Compacting Your MySQL Database}
-\index[general]{Database!Compacting Your MySQL}
-\index[general]{Compacting Your MySQL Database}
+\index[general]{Database!MySQL!Compacting}
 \label{CompactingMySQL}
 
 Over time, as noted above, your database will tend to grow.

manuals/en/main/howto.tex

@@ -604,7 +604,7 @@ \subsubsection{Restores}
 
 
 \subsection{Backup of a PostgreSQL Database}
-\index[general]{PostgreSQL Backup}
+\index[general]{PostgreSQL!Backup}
 \index[general]{Database!PostgreSQL!Backup}
 \label{backup-postgresql}
 
@@ -720,14 +720,16 @@ \subsubsection{Backup of a PostgreSQL Databases by using the PGSQL-Plugin}
 
 
 \subsection{Backup of a MySQL Database}
-\index[general]{MySQL Backup}
+\index[general]{MySQL!Backup}
 \index[general]{Database!MySQL!Backup}
 \label{backup-mysql}
 
 In this section, we describe different methods to do a full backup of a MySQL database.
 
 \subsubsection{Backup of a MySQL Databases by using the Python MySQL plugin}
 \index[general]{Plugin!Python!MySQL Backup}
+\label{backup-mysql-python}
+
 The Pyhton plugin from \url{https://github.com/bareos/bareos-contrib/tree/master/fd-plugins/mysql-python} makes a backup of all or selected 
 MySQL databases from the file-daemon or any other MySQL server.
 

manuals/en/main/install.tex

@@ -249,7 +249,7 @@ \subsubsection{PostgreSQL}
 \end{commands}
 
 
-\subsubsection{MySQL}
+\subsubsection{MySQL/MariaDB}
 Make sure, that \user{root} has direct access to the local MySQL server. 
 Check if the command \command{mysql} connects to the database without defining the password.
 This is the default on RedHat and SUSE distributions. 
@@ -354,7 +354,7 @@ \subsubsection{PostgreSQL}
 
 After this, restart the Bareos Director and verify it starts without problems.
 
-\subsubsection{MySQL}
+\subsubsection{MySQL/MariaDB}
 Make sure, that \user{root} has direct access to the local MySQL server.
 Check if the command \command{mysql} without parameter connects to the database.
 If not, you may be required to adapt your local MySQL config file \file{~/.my.cnf}.

manuals/en/main/plugins.tex

@@ -56,8 +56,10 @@ \subsection{bpipe Plugin}
 \item[plugin] is the name of the plugin with the trailing -fd.so stripped off, so in this case, we would put bpipe in the field.
 
 \item[filepath] specifies the namespace, which for bpipe is the pseudo path and filename under which the backup will be saved. This
-pseudo path and filename will be seen by the user in the restore file tree. For example, if the value is /MySQL/mydump.sql, the data
-backed up by the plugin will be put under that "pseudo" path and filename. You must be careful to choose a naming convention that is unique
+pseudo path and filename will be seen by the user in the restore file tree. For example, if the value is \argument{/MySQL/mydump.sql},
+the data
+backed up by the plugin will be put under that \bquote{pseudo} path and filename.
+You must be careful to choose a naming convention that is unique
 to avoid a conflict with a path and filename that actually exists on your system.
 
 \item[readprogram] for the bpipe plugin specifies the "reader" program that is called by the plugin during backup to read the data. bpipe
@@ -143,7 +145,8 @@ \subsubsection{Command Plugins}
 } 
 \end{bconfig}
 
-This example uses the MySQL\index[general]{MySQL!Backup} plugin from \url{https://github.com/bareos/bareos-contrib/tree/master/fd-plugins/mysql-python} to backup MySQL dumps in addition to \file{/etc}.
+\index[general]{MySQL!Backup}
+This example uses the \ilink{MySQL plugin}{backup-mysql-python} to backup MySQL dumps in addition to \file{/etc}.
 
 \subsubsection{Option Plugins}
 Option plugins are activated in the Options resource of a FileSet definition.

manuals/en/main/programs.tex

@@ -1420,16 +1420,17 @@ \subsection{bareos-dbcheck}
 \end{itemize}
 
 
-If you are using Mysql, bareos-dbcheck will ask you if you want to create temporary
+If you are using MySQL, \command{bareos-dbcheck} will ask you if you want to create temporary
 indexes to speed up orphaned Path and Filename elimination.
 
-If you are using bvfs (e.g. used by \ilink{BAT}{bat}), don't eliminate orphaned path, else you will
+%\index[general]{bvfs}
+If you are using bvfs (e.g. used by \ilink{bareos-webui}{sec:webui}),
+don't eliminate orphaned path, else you will
 have to rebuild \variable{brestore_pathvisibility} and
 \variable{brestore_pathhierarchy} indexes.
-\TODO{verify if orphaned paths are still in use by Bareos}
 
 Normally
-you should never need to run bareos-dbcheck in spite of the
+you should never need to run \command{bareos-dbcheck} in spite of the
 recommendations given above, which are given so that users don't
 waste their time running bareos-dbcheck too often.
 

manuals/en/main/quickstart.tex

@@ -227,15 +227,14 @@ \section{Testing your Configuration Files}
 \index[general]{Testing!Configuration Files}
 
 You can test if your configuration file is syntactically correct by running
-the appropriate daemon with the {\bf -t} option. The daemon will process the
+the appropriate daemon with the \parameter{-t} option. The daemon will process the
 configuration file and print any error messages then terminate.
 
 \begin{commands}{Testing Configuration Files}
 bareos-dir -t -c /etc/bareos/bareos-dir.conf
 bareos-fd -t -c /etc/bareos/bareos-fd.conf
 bareos-sd -t -c /etc/bareos/bareos-sd.conf
 bconsole -t -c /etc/bareos/bconsole.conf
-bat -t -c /etc/bareos/bat.conf
 bareos-tray-monitor -t -c /etc/bareos/tray-monitor.conf
 \end{commands}
 

manuals/en/main/supportedoses.tex

@@ -16,11 +16,11 @@
   Univention Corporate Linux & App Center & v12.4 & v12.4 & v12.4 \\
   \hline
   \hline
-  MS Windows 32bit & 7/8          & v12.4 & \elink{nightly}{http://download.bareos.org/bareos/experimental/nightly/windows/} & \elink{nightly}{http://download.bareos.org/bareos/experimental/nightly/windows/} \\
+  MS Windows 32bit & 7/8/10       & v12.4 & \elink{nightly}{http://download.bareos.org/bareos/experimental/nightly/windows/} & \elink{nightly}{http://download.bareos.org/bareos/experimental/nightly/windows/} \\
   ~                & 2008/Vista   &  &  &  \\
   ~                & XP           &  &         &  \\
   \hline
-  MS Windows 64bit & 7/2012/8     & v12.4 & \elink{nightly}{http://download.bareos.org/bareos/experimental/nightly/windows/} & \elink{nightly}{http://download.bareos.org/bareos/experimental/nightly/windows/} \\
+  MS Windows 64bit & 7/2012/8/10  & v12.4 & \elink{nightly}{http://download.bareos.org/bareos/experimental/nightly/windows/} & \elink{nightly}{http://download.bareos.org/bareos/experimental/nightly/windows/} \\
   ~                & 2008/Vista   &  &  &  \\
   \hline
   \hline