Some doc updates

[bacula/docs] / docs / manual / rpm-faq.tex

diff --git a/docs/manual/rpm-faq.tex b/docs/manual/rpm-faq.tex
index 1fa1d76a78647ea1e4115e9e5018e84842a1f4a3..44383d64965275315e0ca2c3ecbb9c7c86f26074 100644 (file)
--- a/docs/manual/rpm-faq.tex
+++ b/docs/manual/rpm-faq.tex
@@ -205,7 +205,15 @@ creation of debug rpm packages is:
 
 \item 
    \label{faq8}
-   {\bf I just upgraded from 1.36.x to 1.38.x and now my director daemon won't start. It appears to start but dies silently and I get a "connection refused" error when starting the console. What is wrong?} Beginning with 1.38 the rpm packages are configured to run the director and storage daemons as a non-root user. The file daemon runs as user root and group bacula, the storage daemon as user bacula and group disk, and the director as user bacula and group bacula. If you are upgrading you will need to change some file permissions for things to work. Execute the following commands as root:
+   {\bf I just upgraded from 1.36.x to 1.38.x and now my director daemon
+won't start.  It appears to start but dies silently and I get a "connection
+refused" error when starting the console.  What is wrong?} Beginning with
+1.38 the rpm packages are configured to run the director and storage
+daemons as a non-root user.  The file daemon runs as user root and group
+bacula, the storage daemon as user bacula and group disk, and the director
+as user bacula and group bacula.  If you are upgrading you will need to
+change some file permissions for things to work.  Execute the following
+commands as root:
 
 \footnotesize
 \begin{verbatim}
@@ -216,11 +224,20 @@ creation of debug rpm packages is:
 \end{verbatim}
 \normalsize
 
-Further, if you are using File storage volumes rather than tapes those files will also need to have ownership set to user bacula and group bacula.
+Further, if you are using File storage volumes rather than tapes those
+files will also need to have ownership set to user bacula and group bacula.
 
 \item 
    \label{faq9}
-   {\bf There are a lot of rpm packages. Which packages do I need for what?} For a bacula server you need to select the packsge based upon your preferred catalog database: one of bacula-mysql, bacula-postgresql or bacula-sqlite.  If your system does not provide an mtx package you also need bacula-mtx to satisfy that dependancy.  For a client machine you need only install bacula-client.  Optionally, for either server or client machines, you may install a graphical console bacula-gconsole and/or bacula-wxconsole. One last package, bacula-updatedb is required only when upgrading a server more than one database revision level.
+   {\bf There are a lot of rpm packages.  Which packages do I need for
+what?} For a bacula server you need to select the packsge based upon your
+preferred catalog database: one of bacula-mysql, bacula-postgresql or
+bacula-sqlite.  If your system does not provide an mtx package you also
+need bacula-mtx to satisfy that dependancy.  For a client machine you need
+only install bacula-client.  Optionally, for either server or client
+machines, you may install a graphical console bacula-bgnome-console and/or
+bacula-bwxconsole.  One last package, bacula-updatedb is required only when
+upgrading a server more than one database revision level.
 
 
 
@@ -316,12 +333,12 @@ Build the client rpm only in place of one of the above database full builds:
 X86-64 support:
 --define "build_x86_64 1"
 
-Supress build of gnome-console:
---define "nobuild_gconsole 1"
+Supress build of bgnome-console:
+--define "nobuild_bgconsole 1"
 
 Build the WXWindows console:
 requires wxGTK >= 2.6
---define "build_wxconsole 1"
+--define "build_bwxconsole 1"
 
 Build python scripting support:
 --define "build_python 1"