Mention in docs typical syslog configuration, which drops syslog messages with debug...

diff --git a/org.glite.lb.doc/src/LBAG-Installation.tex b/org.glite.lb.doc/src/LBAG-Installation.tex
index afd48ce..d3445f2 100644 (file)
--- a/org.glite.lb.doc/src/LBAG-Installation.tex
+++ b/org.glite.lb.doc/src/LBAG-Installation.tex
@@ -110,7 +110,7 @@ A file \texttt{log4crc.example-debugging} may be useful to copy to
 \texttt{\$HOME/.log4crc} (or by setting the \texttt{LOG4C\_RCPATH} environment variable
 to a directory containing the \texttt{log4crc} file) to obtain detailed debugging output.
 One can debug only specific parts of the LB system, for example
-by uncommenting \texttt{LB.SERVER.DB} cathegory in the \texttt{log4crc} file,
+by uncommenting \texttt{LB.SERVER.DB} category in the \texttt{log4crc} file,
 one gets only the debugging info related to the underlying database subsystem calls.
 
 
@@ -134,7 +134,12 @@ LB.AUTHZ & Authentication matters \\
 
 The following log priorities are recognized, in a descending order of severity: \texttt{fatal}, \texttt{error}, \texttt{warn}, \texttt{info}, \texttt{debug}. Note that running with any of the logging categories set do \texttt{debug} for a prolonged period of time will result in the logfile growing uncontroledly.
 
-In a typical setup, logging messages generated by the \LB service will be found in \texttt{/var/log/messages}. 
+In a typical setup, logging messages generated by the \LB service will be found in \texttt{/var/log/messages}.
+
+Note, sylog is typically configured to drop log messages with \texttt{debug} priority. You may want to enable it, for example using something like that in \texttt{/etc/syslog.conf}:
+\begin{verbatim}
+*debug;mail.none;authpriv.none;cron.none                -/var/log/messages
+\end{verbatim}
 
 \subsection{\LB server}