Client Initiated Connection: using local log file

bareos · Jan 27, 2017 · 5d06015 · 5d06015
1 parent b3a1283
commit 5d06015
Show file tree

Hide file tree

Showing 2 changed files with 17 additions and 2 deletions.
diff --git a/manuals/en/main/client-initiated-connection.tex b/manuals/en/main/client-initiated-connection.tex
@@ -54,4 +54,19 @@ \section{Client Initiated Connection}
 If none of this worked, the job fails.
 
 When a waiting connection is used for a job, the \bareosFd will detect this and creates an additional connection.
-This is required, to keep the client responsive for additional commands, like \bcommand{cancel}.
+This is required, to keep the client responsive for additional commands, like \bcommand{cancel}{}.
+
+To get feedback in case the \bareosFd fails to connect to the \bareosDir, consider configuring \bareosFd to log in a local file.
+This can be archived by adding the line
+
+\configline{Append = "/var/log/bareos/bareos-fd.log" = all, !skipped, !restored}
+
+to the default message resource \resourcename{Fd}{Messages}{Standard}:
+
+\begin{bareosConfigResource}{bareos-fd}{messages}{Standard}
+Messages {
+  Name = Standard
+  Director = bareos-dir = all, !skipped, !restored
+  Append = "/var/log/bareos/bareos-fd.log" = all, !skipped, !restored
+}
+\end{bareosConfigResource}
diff --git a/manuals/en/main/messagesres.tex b/manuals/en/main/messagesres.tex
@@ -136,7 +136,7 @@ \section{Message Types}
 
 \item [volmgmt] \hfill \\
 \index[general]{Messages!type!volmgmt}
-Volume management messages. Currently there are no volume mangement
+Volume management messages. Currently there are no volume management
 messages generated.
 
 \item [audit] \hfill \\