From faadebe01fa0838439068c325c6311ff95d8fe81 Mon Sep 17 00:00:00 2001
From: =?utf8?q?Zden=C4=9Bk=20=C5=A0ustr?= <sustr4@cesnet.cz>
Date: Thu, 26 May 2011 14:16:21 +0000
Subject: [PATCH] Extended information on logging.

---
 org.glite.lb.doc/src/LBAG-Installation.tex | 23 +++++++++++++++++++++++
 org.glite.lb.doc/src/LBAG-Running.tex      |  4 ++++
 2 files changed, 27 insertions(+)

diff --git a/org.glite.lb.doc/src/LBAG-Installation.tex b/org.glite.lb.doc/src/LBAG-Installation.tex
index 7ec921d..afd48ce 100644
--- a/org.glite.lb.doc/src/LBAG-Installation.tex
+++ b/org.glite.lb.doc/src/LBAG-Installation.tex
@@ -92,6 +92,7 @@ where all \verb'glite-lbjp-common-*' packages are common both to \LB and
 Job Provenance (\JP).
 
 \subsection{Common logging format}
+\label{inst:comlog}
 Since \LBver{2.1} \LB service follows the \textbf{gLite common logging recommendations v1.1}:
 \begin{center}
 \url{https://twiki.cern.ch/twiki/pub/EGEE/EGEEgLite/logging.html}. 
@@ -113,6 +114,28 @@ by uncommenting \texttt{LB.SERVER.DB} cathegory in the \texttt{log4crc} file,
 one gets only the debugging info related to the underlying database subsystem calls.
 
 
+Currently supported log categories are:
+
+\begin{tabularx}{\textwidth}{>{\tt}lX}
+SECURITY & Security matters \\
+ACCESS & Communication issues \\
+CONTROL & \LB server control \\
+LB & \emph{unused} \\
+LB.LOGD & Messages from the \LB local logger \\
+LB.INTERLOGD & Messages from the \LB interlogger \\
+LB.NOTIFINTERLOGD & Messages from the notification interlogger \\
+LB.SERVER & Processing within the \LB server \\
+LB.SERVER.DB & DB calls made by the server \\
+LB.SERVER.REQUEST & Processing \LB server requests \\
+LB.HARVESTER & Messages from the \LB harvester \\
+LB.HARVESTER.DB & DB calls made by the harvester \\
+LB.AUTHZ & Authentication matters \\
+\end{tabularx}
+
+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}. 
+
 \subsection{\LB server}
 
 \subsubsection{Hardware requirements}
diff --git a/org.glite.lb.doc/src/LBAG-Running.tex b/org.glite.lb.doc/src/LBAG-Running.tex
index 5649ef0..ee710da 100644
--- a/org.glite.lb.doc/src/LBAG-Running.tex
+++ b/org.glite.lb.doc/src/LBAG-Running.tex
@@ -35,6 +35,10 @@ as standard manual pages installed with the \LB packages.
 In normal operation \LB server sends error messages to syslog.
 Informational messages are generally avoided in order to prevent syslog congestion.
 
+Since \LBver{2.1}, the service implements a common logging format\footnote{\url{http://en.wikipedia.org/wiki/Common_Log_Format}} (see section\,\ref{inst:comlog}, page\,\pageref{inst:comlog}).
+
+For \LBver{2.0 and lower}, the following instructions apply:
+
 \begin{sloppypar}
 When tracing problems, GLITE\_LB\_SERVER\_DEBUG environment variable can be set to
 non-empty value when starting the service.
-- 
1.8.2.3