Updates

diff --git a/docs/manual/console.tex b/docs/manual/console.tex
index b595041c401d0d1c73b385ca846d4448add10a9f..8a6ed14ce2c2f4dd693f429e3970f4e05887774a 100644 (file)
--- a/docs/manual/console.tex
+++ b/docs/manual/console.tex
@@ -909,23 +909,29 @@ time. Use the {\bf mod} option and select {\bf When} (no. 6).  Then enter the
 desired start time in YYYY-MM-DD HH:MM:SS format.  
 
 \item [setdebug]
+   \index[console]{setdebug}
    \index[dir]{setdebug}
+   \index[dir]{debugging}
+   \index[dir]{debugging Win32}
+   \index[dir]{Windows!debugging}
    This command is used to set the debug level in each  daemon. The form of this
    command is:
 
 setdebug level=nn [trace=0/1 client=\lt{}client-name\gt{} | dir | director |
   storage=\lt{}storage-name\gt{} | all]  
 
-   If trace=1 is set, then the tracing will be enabled, and the daemon
-   where the setdebug applies will be placed in trace mode, and all debug
-   output will go to the file {\bf bacula.trace} in the current directory
-   of the daemon.  Normally, tracing is used only for Win32 clients where
-   the debug output cannot be written to a terminal or redirected to a
-   file.  When tracing, each debug output message is appended to the trace
-   file.  You must explicitly delete the file when you are done.
+   If trace=1 is set, then tracing will be enabled, and the daemon will be
+   placed in trace mode, which means that all debug output as set by the
+   debug level will be directed to the file {\bf bacula.trace} in the
+   current directory of the daemon.  Normally, tracing is needed only for
+   Win32 clients where the debug output cannot be written to a terminal or
+   redirected to a file.  When tracing, each debug output message is
+   appended to the trace file.  You must explicitly delete the file when
+   you are done.
 
 \item [show]
    \index[console]{show}
+   \index[dir]{show}
    The show command will list the Director's resource records as defined in
    the Director's configuration file (normally {\bf bacula-dir.conf}).
    This command is used mainly for debugging purposes by developers.     
@@ -936,7 +942,7 @@ setdebug level=nn [trace=0/1 client=\lt{}client-name\gt{} | dir | director |
    with the {\bf list}, which displays the contents of the catalog.
 
 \item [sqlquery]
-   \index[dir]{sqlquery}
+   \index[console]{sqlquery}
    The sqlquery command puts the Console program into SQL query mode where
    each line you enter is concatenated to the previous line until a
    semicolon (;) is seen.  The semicolon terminates the command, which is

diff --git a/docs/manual/critical.tex b/docs/manual/critical.tex
index 563d382aaed7635ea7f2e2b8ff6e38e16764fe19..c299db8875dc715377deed4adf19f8a4a49ac29a 100644 (file)
--- a/docs/manual/critical.tex
+++ b/docs/manual/critical.tex
@@ -44,7 +44,7 @@ production system (if you already are in production, use the checklist anyway).
 \item Better than doing the above is to walk through the nine steps in the  
    \ilink{Tape Testing}{_ChapterStart27} chapter of the manual. It 
    may take you a bit of time, but it will eliminate surprises. 
-\item Test your the end of tape handling of your tape drive by using the
+\item Test the end of tape handling of your tape drive by using the
    fill command in the \ilink{btape}{btape} program.
 \item If you are using a 2.4 kernel, make sure that /lib/tls is disabled. Bacula
    does not work with this library. See the second point under 
@@ -76,8 +76,6 @@ production system (if you already are in production, use the checklist anyway).
    CDROM}{_ChapterRescue} chapter. It is trivial to  make such a CDROM,
    and it can make system recovery in the event of  a lost hard disk infinitely
    easier. 
-\item After doing your first backup restore some or all the data.  Do this for
-   at least one client on each different OS (e.g. Linux, FreeBSD, Solaris, Win32).
 \end{itemize}
 
 \subsection*{Recommended Items}