Remove reference to SQLite from manual

[bacula/docs] / docs / manuals / en / main / dirdconf.tex

diff --git a/docs/manuals/en/main/dirdconf.tex b/docs/manuals/en/main/dirdconf.tex
index ab3cda8dd3b0a0bf694ffdddd2ea4740f0f0a76b..032075444c91977c6189481801a78545ab3fbedc 100644 (file)
--- a/docs/manuals/en/main/dirdconf.tex
+++ b/docs/manuals/en/main/dirdconf.tex
@@ -3182,16 +3182,14 @@ the Pool currently being used by the job.
 \index[general]{Catalog Resource}
 
 The Catalog Resource defines what catalog to use for the current job.
-Currently, Bacula can only handle a single database server (SQLite, MySQL,
+Currently, Bacula can only handle a single database server (MySQL or
 PostgreSQL) that is defined when configuring {\bf Bacula}.  However, there
 may be as many Catalogs (databases) defined as you wish.  For example, you
 may want each Client to have its own Catalog database, or you may want
 backup jobs to use one database and verify or restore jobs to use another
 database. 
 
-Since SQLite is compiled in, it always runs on the same machine
-as the Director and the database must be directly accessible (mounted) from
-the Director.  However, since both MySQL and PostgreSQL are networked
+Since both MySQL and PostgreSQL are networked
 databases, they may reside either on the same machine as the Director
 or on a different machine on the network.  See below for more details.
 
@@ -3237,7 +3235,7 @@ defined.
    \index[dir]{DB Socket}
    \index[dir]{Directive!DB Socket}
    This is the name of  a socket to use on the local host to connect to the
-   database. This directive is used only by MySQL and is ignored by  SQLite.
+   database. This directive is used only by MySQL.
    Normally, if neither {\bf DB Socket} or {\bf DB Address}  are specified, MySQL
    will use the default socket. If the DB Socket is specified, the
    MySQL server must reside on the same machine as the Director.
@@ -3248,7 +3246,7 @@ defined.
    This is the host address  of the database server. Normally, you would specify
    this instead  of {\bf DB Socket} if the database server is on another machine.
    In that case, you will also specify {\bf DB Port}. This directive  is used
-   only by MySQL and PostgreSQL and is ignored by SQLite if provided.  
+   only by MySQL and PostgreSQL.
    This directive is optional.  
 
 \item [DB Port = \lt{}port\gt{}]
@@ -3256,7 +3254,7 @@ defined.
    \index[dir]{Directive!DBPort}
    This defines the port to  be used in conjunction with {\bf DB Address} to
    access the  database if it is on another machine. This directive is used  only
-   by MySQL and PostgreSQL and is ignored by SQLite if provided.  This
+   by MySQL and PostgreSQL.
    directive is optional.
 
 %% \item [Multiple Connections = \lt{}yes\vb{}no\gt{}]
@@ -3267,14 +3265,14 @@ the
 %% same Catalog will use a single connection to the catalog. It will  be shared,
 %% and Bacula will allow only one Job at a time to  communicate. If you set this
 %% directive to yes, Bacula will  permit multiple connections to the database,
-%% and the database  must be multi-thread capable. For SQLite and PostgreSQL,
+%% and the database  must be multi-thread capable. For and PostgreSQL,
 %% this is  no problem. For MySQL, you must be *very* careful to have the 
 %% multi-thread version of the client library loaded on your system.  When this
 %% directive is set yes, each Job will have a separate  connection to the
 %% database, and the database will control the  interaction between the
 different
 %% Jobs. This can significantly  speed up the database operations if you are
-%% running multiple  simultaneous jobs. In addition, for SQLite and PostgreSQL,
+%% running multiple  simultaneous jobs. In addition, for and PostgreSQL,
 %% Bacula  will automatically enable transactions. This can significantly  speed
 %% up insertion of attributes in the database either for  a single Job or
 %% multiple simultaneous Jobs.  
@@ -3290,7 +3288,7 @@ The following is an example of a valid Catalog resource definition:
 \begin{verbatim}
 Catalog
 {
-  Name = SQLite
+  Name = MySQL
   dbname = bacula;
   user = bacula;
   password = ""                       # no password = no security