TODOs and minor hands-on editing

diff --git a/org.glite.lb.doc/src/LBAG-Installation.tex b/org.glite.lb.doc/src/LBAG-Installation.tex
index 9748415..1aad4ec 100644 (file)
--- a/org.glite.lb.doc/src/LBAG-Installation.tex
+++ b/org.glite.lb.doc/src/LBAG-Installation.tex
@@ -11,6 +11,8 @@ distribute the software in other distribution formats, e.g. DEB packages.
 
 In \LBold, the list of all LB packages was the following:
 
+\TODO{ljocha: vylepsit popisky, taky do zdrojaku}
+
 \begin{tabularx}{\textwidth}{>{\tt}lX}
 glite-lb-common & LB common files \\ 
 glite-lb-client & LB client library \\ 
@@ -81,6 +83,8 @@ day where all jobs are purged after 10 days needs about 58
 ($10 \cdot 40000 \cdot 0.000000120 + 10$) gigabytes (not accounting for operating 
 system and system logs).
 
+\TODO{salvet: vylepsit citelnost formulky}
+
 For smooth handling of 40\,000 jobs/day, this or better machine configuration 
 is necessary:
 \begin{itemize}
@@ -103,6 +107,8 @@ offered load.
 
 \subsubsection{Standard installation}
 
+\TODO{valtri: odkazy na metapackage a repository, zkusit najit oficialni gLite dokumentaci}
+
 After installation and configuration of OS and basic services
 (certificates, CAs, time synchronization), glite-LB metapackage 
 from appropriate gLite sotware repository should be installed.

diff --git a/org.glite.lb.doc/src/LBAG-Introduction.tex b/org.glite.lb.doc/src/LBAG-Introduction.tex
index fddad7a..604d2c3 100644 (file)
--- a/org.glite.lb.doc/src/LBAG-Introduction.tex
+++ b/org.glite.lb.doc/src/LBAG-Introduction.tex
@@ -26,8 +26,8 @@ and delivering the events to \LB servers where users can query for them
 \label{f:comp-query}
 \end{figure}
 
-\TODO{uplne to same (ty components) mame i v UG; chceme to tady duplikovat? 
-zvlast kdyz v odstavci nad tim se pise, ze uz je to popsane v UG}
+%\TODO{uplne to same (ty components) mame i v UG; chceme to tady duplikovat? 
+%vlast kdyz v odstavci nad tim se pise, ze uz je to popsane v UG}
 \input components
 
 

diff --git a/org.glite.lb.doc/src/LBDG-Introduction.tex b/org.glite.lb.doc/src/LBDG-Introduction.tex
index b9b08cf..b40aafd 100644 (file)
--- a/org.glite.lb.doc/src/LBDG-Introduction.tex
+++ b/org.glite.lb.doc/src/LBDG-Introduction.tex
@@ -42,6 +42,8 @@ other languages, as the C constructs often reflect directly.
 
 \subsection{General Guidelines}
 
+\TODO{kde se vzalo edg}
+
 \marginpar{Naming conventions}%
 All names exported by the \LB library (function names, symbolic
 constants) are prefixed to avoid name clashes. The prefix is
@@ -89,15 +91,13 @@ much as possible. In a few cases the error can not be intuitively
 mapped and \LB specific error value greater than
 \verb'EDG_WLL_ERROR_BASE' is returned.
 
-\TODO{mozna by stalo za to zminit f-ce edg\_wll\_*Error*}
-
 Few API function return \verb'char *'. In such a~case
 \verb'NULL' indicates an error, non-null value means success.
 
 \subsection{Context and Parameter Settings}
 \label{s:context}
 
-The \LB library does not maintain internal state, all the API
+The \LB library does not maintain internal state (apart of network connections, see \ref{s:pool}), all the API
 functions refer to a~\emph{context} argument instead.
 Context object preserves state information among the various API
 calls, the state including \LB library parameters (\eg security
@@ -130,6 +130,7 @@ The context object and its API functions are described more thoroughly
 in section~\ref{s:edg_wll_context}
 
 \subsection{Connection Pool}
+\label{s:pool}
 The \LB library maintains pool of client--server connections to
 improve performance (creating SSL connection is heavy--weight
 operation). The connections are transparently shared and reused by all

diff --git a/org.glite.lb.doc/src/LBDG.tex b/org.glite.lb.doc/src/LBDG.tex
index 2bef07d..b67fe98 100644 (file)
--- a/org.glite.lb.doc/src/LBDG.tex
+++ b/org.glite.lb.doc/src/LBDG.tex
@@ -3,7 +3,7 @@
 \def\insideDG{}
 
 \input{definitions}
-\def\LB{LB\xspace}
+%\def\LB{LB\xspace}
 
 \title{Logging and Bookkeeping}
 \Subtitle{Developer's Guide}

diff --git a/org.glite.lb.doc/src/LBUG-Tools.tex b/org.glite.lb.doc/src/LBUG-Tools.tex
index 8df4d8d..1906524 100644 (file)
--- a/org.glite.lb.doc/src/LBUG-Tools.tex
+++ b/org.glite.lb.doc/src/LBUG-Tools.tex
@@ -3,9 +3,11 @@
 
 In this section we give a description of the CLI tools that a regular grid user
 might want to use. If not stated otherwise, the tools are distributed in the
-\verb'glite-lb-client' RPM. Behaviour of the commands can be often changed by
+\verb'glite-lb-client' RPM. Behaviour of the commands can be changed by
 setting some of the following enviroment variables:
 
+\TODO{ruda: tady kapitolku, ze prostredi je dulezite, odkaz na appendix, kde bude vsechno. common/src/param.c}
+
 \begin{tabularx}{\textwidth}{lX}
 GLITE\_WMS\_LOG\_DESTINATION & address of \verb'glite-lb-logd' daemon, in form \verb'hostname:port', for logging events\\
 GLITE\_WMS\_LOG\_TIMEOUT & timeout (in seconds) for asynchronous logging\\

diff --git a/org.glite.lb.doc/src/notify.tex b/org.glite.lb.doc/src/notify.tex
index 12eba4c..af1d67d 100644 (file)
--- a/org.glite.lb.doc/src/notify.tex
+++ b/org.glite.lb.doc/src/notify.tex
@@ -20,7 +20,7 @@ However, only a single active client for a notification is allowed.
 \LB server and port to contact is specified with GLITE\_WMS\_NOTIF\_SERVER 
 environment variable.
 
-\TODO{ruda, what's supported in \LBold, what in \LBnew}
+\TODO{ruda, what's supported in \LBold (jen example), what in \LBnew}
 
 \verb'glite-lb-notify' support these actions:
 
@@ -90,8 +90,11 @@ Register notification for given jobid:
 \begin{verbatim}
    GLITE_WMS_NOTIF_SERVER=skurut68-2.cesnet.cz:9100 bin/glite-lb-notify new \
     -j https://skurut68-2.cesnet.cz:9100/D1qbFGwvXLnd927JOcja1Q
+\end{verbatim}
 
    returns:
+
+\begin{verbatim}
    notification ID: https://skurut68-2.cesnet.cz:9100/NOTIF:tOsgB19Wz-M884anZufyUw 
 \end{verbatim}