extend debug messages description

manuals/en/main/bconsole.tex

@@ -1225,7 +1225,7 @@ \section{Console Commands}
 
 
 \item [setdebug]
-    \label{bcommandSetdebug}
+   \label{bcommandSetdebug}
    \index[general]{Console!Command!setdebug}
    \index[general]{Debug!setdebug}
    \index[general]{Debug!Windows}
@@ -1254,13 +1254,16 @@ \section{Console Commands}
 
    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 \file{bareos.trace} in the
-   current directory of the daemon.  Normally, tracing is needed only for
-   Windows clients where the debug output cannot be written to a terminal or
-   redirected to a file.  When tracing, each debug output message is
+   debug level will be directed to his trace file in the
+   current directory of the daemon.  When tracing, each debug output message is
    appended to the trace file.  You must explicitly delete the file when
    you are done.
 
+\begin{bconsole}{set Director debug level to 100 and get messages written to his trace file}
+*<input>setdebug level=100 trace=1 dir</input>
+level=100 trace=1 hangup=0 timestamp=0 tracefilename=/var/lib/bareos/bareos-dir.example.com.trace
+\end{bconsole}
+
 \item [setip]
    \index[general]{Console!Command!setip}
    Sets new client address -- if authorized.

manuals/en/main/debug.tex

@@ -2,10 +2,13 @@
 %%
 
 %\chapter{What To Do When Bareos Crashes (Kaboom)}
-\label{debug}
 \index[general]{Crash}
 \index[general]{Debug!crash}
 
+This chapter describes, how to debug Bareos, when the program crashes.
+If you are just interested about how to get more information about a running Bareos daemon,
+please read \nameref{sec:debug-messages}.
+
 If you are running on a Linux system, and you have a set of working
 configuration files, it is very unlikely that {\bf Bareos} will crash. As with
 all software, however, it is inevitable that someday, it may crash.
@@ -110,8 +113,8 @@ \section{Manually Running Bareos Under The Debugger}
 \item Start the Storage daemon under the debugger:
 
 \begin{commands}{run the Bareos Storage daemon in the debugger}
-<command>gdb</command><parameter> /usr/sbin/bareos-sd</parameter>
-(gdb) <input>run -f -s -d 200</input>
+<command>gdb</command><parameter> --args /usr/sbin/bareos-sd -f -s -d 200</parameter>
+(gdb) <input>run</input>
 \end{commands}
 
 Parameter:

manuals/en/main/troubleshooting.tex

@@ -1,9 +1,16 @@
 
+\section{Debug Messages}
+\label{sec:debug-messages}
+
+The Bareos programs contain a lot of debug messages. Normally, these are not printed.
+See the \ilink{setdebug}{bcommandSetdebug} chapter about how to enable them.
+
+
 \section{Client Access Problems}
 \label{AccessProblems}
 \index[general]{Cannot Access a Client}
    There are several reasons why Bareos could not contact a client  on a
-   different machine. They are:  
+   different machine. They are:
 
 \begin{itemize}
 \item Check if the client file daemon is really running.
@@ -13,7 +20,7 @@ \section{Client Access Problems}
 \item You have a firewall, and it is blocking traffic on port  9102 between
    the Director's machine and the Client's  machine (or on port 9103 between the
    Client and the Storage daemon  machines). 
-\item If your system is using Tcpwrapper ({\bf hosts.allow} or {\bf hosts.deny} file), verify that is
+\item If your system is using Tcpwrapper (\file{hosts.allow} or \file{hosts.deny} file), verify that is
    permitting access.
 \item Your password or names are not correct in both the Director and  the
    Client machine. Try configuring everything identical to  how you run the
@@ -789,10 +796,6 @@ \subsection{Restoring When Things Go Wrong}
 \end{enumerate}
 
 When the above is complete, you can begin bscanning your Volumes. Please
-see the \ilink{bscan}{bscan} section of the Volume Utility Tools of this
-chapter for more details.
+see the \nameref{bscan} chapter for more details.
 
 \end{description}
-
-
-\TODO{add the debug chapter?}