From 7f109f0c0129aa24038667d774e248cad1441fc4 Mon Sep 17 00:00:00 2001
From: Kern Sibbald <kern@sibbald.com>
Date: Thu, 4 May 2006 13:20:12 +0000
Subject: [PATCH] Final changes

---
 docs/manual/install.tex     |  8 +++++++-
 docs/manual/tapetesting.tex | 36 ++++++++++++++++++++++++++++--------
 2 files changed, 35 insertions(+), 9 deletions(-)

diff --git a/docs/manual/install.tex b/docs/manual/install.tex
index 317c1305..b0b45a45 100644
--- a/docs/manual/install.tex
+++ b/docs/manual/install.tex
@@ -253,6 +253,9 @@ machine to another. If the {\bf make distclean} fails,  just ignore it and
 continue on.  
 
 \item make  
+\begin{verbatim}
+
+\end{verbatim}
    If you get errors while linking in the Storage daemon directory
    (src/stored), it is probably because you have not loaded the static
    libraries on your system.  I noticed this problem on a Solaris system.
@@ -283,7 +286,9 @@ continue on.
    can be done after you have Bacula up and running.  Please take care when
    modifying passwords, which were randomly generated, and the {\bf Name}s
    as the passwords and names must agree between the configuration files
-   for security reasons.  \item Create the Bacula MySQL database and tables
+   for security reasons.  
+
+\item Create the Bacula MySQL database and tables
    (if using MySQL)
       \ilink{Installing and Configuring MySQL Phase II}{mysql_phase2} or 
       create the Bacula PostgreSQL database and tables  
@@ -303,6 +308,7 @@ continue on.
    heavy modifications to the  configuration files so that you are sure that
    Bacula works  and are familiar with it. After that changing the conf files 
    will be easier.  
+
 \item If after installing Bacula, you decide to "move it", that is  to
    install it in a different set of directories, proceed  as follows:  
 
diff --git a/docs/manual/tapetesting.tex b/docs/manual/tapetesting.tex
index 0988b28a..faede97a 100644
--- a/docs/manual/tapetesting.tex
+++ b/docs/manual/tapetesting.tex
@@ -900,14 +900,11 @@ Device {
 \normalsize
 
 
-\subsubsection*{Determining What Tape Drives and Autochangers You Have on
-FreeBSD}
-\index[general]{FreeBSD!Determining What Tape Drives and Autochangers You Have
-}
-\index[general]{Determining What Tape Drives and Autochangers You Have on
-FreeBSD}
-\addcontentsline{toc}{subsubsection}{Determining What Tape Drives and
-Autochangers You Have on FreeBSD}
+\subsubsection*{Finding your Tape Drives and Autochangers on FreeBSD}
+\index[general]{FreeBSD!Finding your Tape Drives and Autochangers}
+\index[general]{Finding your Tape Drives and Autochangers on FreeBSD}
+\addcontentsline{toc}{subsubsection}{Finding your Tape Drives and
+Autochangers on FreeBSD}
 
 On FreeBSD, you can do a {\bf camcontrol devlist} as root to determine what
 drives and autochangers you have. For example, 
@@ -1186,3 +1183,26 @@ your Storage daemon can access the device. You need to ensure that you
 all access to the proper control device, and if you don't have any
 SCSI disk drives (including SATA drives), you might want to change
 the permissions on /dev/sg*.
+
+\subsection*{Syslog Errors}
+\index[general]{Errors!Syslog}
+\index[general]{Syslog Errors}
+\addcontentsline{toc}{subsection}{Syslog Errors}
+
+If you are getting errors such as:
+
+\footnotesize
+\begin{verbatim}
+: kernel: st0: MTSETDRVBUFFER only allowed for root
+\end{verbatim}
+\normalsize
+
+you are most likely running your Storage daemon as non-root, and
+Bacula is attempting to set the correct OS buffering to correspond
+to your Device resource. Most OSes allow only root to issue this
+ioctl command. In general, the message can be ignored providing 
+you are sure that your OS parameters are properly configured as
+described earlier in this manual.  If you are running your Storage daemon 
+as root, you should not be getting these system log messages, and if
+you are, something is probably wrong.
+
-- 
2.39.5