removed several overfull hboxes

diff --git a/org.glite.lb.doc/src/LBAG-Installation.tex b/org.glite.lb.doc/src/LBAG-Installation.tex
index 59dfc1b..f9941b7 100644 (file)
--- a/org.glite.lb.doc/src/LBAG-Installation.tex
+++ b/org.glite.lb.doc/src/LBAG-Installation.tex
@@ -309,11 +309,11 @@ Can be invoked from any machine.
 
 \how 
 \begin{quote}
-\verb'/opt/glite/examples/glite-lb-job_reg -m' \emph{my.server.name:port}
+\verb'/opt/glite/examples/glite-lb-job_reg -m' \emph{server\_name:port}
 \end{quote}
 A~new jobid is generated and printed.  Run 
 \begin{quote}
-\verb'/opt/glite/examples/glite-lb-job_status' \emph{the\_\/new\_\/jobid}
+\verb'/opt/glite/examples/glite-lb-job_status' \emph{jobid}
 \end{quote}
 
 \result
@@ -332,13 +332,13 @@ Must be run on a~machine where glite-lb-logger package is set up and running.
 
 \how
 \begin{quote}
-\verb'/opt/glite/examples/glite-lb-running.sh -m ' \emph{my.server.name:port}
+\verb'/opt/glite/examples/glite-lb-running.sh -m ' \emph{server\_name:port}
 \end{quote}
 
 The command prints a~new jobid, followed by diagnostic messages as the events are logged. 
 Check the status of the new job with
 \begin{quote}
-\verb'/opt/glite/examples/glite-lb-job_status' \emph{the\_\/new\_\/jobid}
+\verb'/opt/glite/examples/glite-lb-job_status' \emph{jobid}
 \end{quote}
 
 \result
@@ -357,12 +357,12 @@ options.
 
 \how Similar to Sect.~\ref{smoke-log}:
 \begin{quote}
-\verb'/opt/glite/examples/glite-lb-running.sh -x -m ' \emph{my.server.name:port}
+\verb'/opt/glite/examples/glite-lb-running.sh -x -m ' \emph{server\_name:port}
 \end{quote}
 
 And check with:
 \begin{quote}
-\verb'/opt/glite/examples/glite-lb-job_status -x /tmp/lb_proxy_server.sock' \emph{the\_\/new\_\/jobid}
+\verb'/opt/glite/examples/glite-lb-job_status -x /tmp/lb_proxy_server.sock' \emph{jobid}
 \end{quote}
 
 

diff --git a/org.glite.lb.doc/src/LBAG-Running.tex b/org.glite.lb.doc/src/LBAG-Running.tex
index 72fc104..a87fc6a 100644 (file)
--- a/org.glite.lb.doc/src/LBAG-Running.tex
+++ b/org.glite.lb.doc/src/LBAG-Running.tex
@@ -160,7 +160,7 @@ queries which should not disturb normal operation), disadvantage is
 a~more complex and more fragile setup. 
 
 Using an external utility \verb'glite-lb-dump' (typical invocation is with
-a~single option \verb'-m' \emph{my.server.name:port}, see man page for
+a~single option \verb'-m' \emph{server\_name:port}, see man page for
 details) the server is triggered to dump events, which arrived in
 a~specified time interval, into a~text file. (Default interval is from last
 dump till the current time.)
@@ -428,7 +428,7 @@ histogram:
 \end{verbatim}
 \end{itemize}
 The command \verb'glite-lb-job_status' is a low level query program that can be
-found in the \verb'glite-lb-client' package among examples.
+found in the package \verb'glite-lb-client' among examples.
 
 
 %\subsection{\LB proxy}
@@ -558,8 +558,8 @@ By default \LB server runs as one master process,
 and 10 slave processes.
 Threads are not used.
 
-Master pid is stored in \verb'$HOME/edg-bkserverd.pid' (\LBold),
-\verb'$HOME/glite-lb-bkserverd.pid' (\LBnew).
+Master pid is stored in the file \verb'$HOME/edg-bkserverd.pid' (\LBold)
+or in the file \verb'$HOME/glite-lb-bkserverd.pid' (\LBnew) respectively.
 Number of slaves can be set with \verb'-s, --slaves' option,
 pid file location with~\verb'-i, --pidfile'.
 
@@ -596,7 +596,7 @@ the pid file.
 Server data are stored in MySQL database. Normal setup assumes ``server scenario'', 
 \ie the database IS NOT protected with password and it is not accessible over network.
 Option \verb'-m user/password@machine:database' can be used to change
-the default \verb'lbserver/@localhost:lbserver20'.
+the default connect string \verb'lbserver/@localhost:lbserver20'.
 
 \item[Dump files.]
 Backup dump (Sect.~\ref{run:dump}) files are stored in
@@ -607,7 +607,7 @@ go to \verb'/tmp/purge' by default, and startup script uses \verb'--purge-prefix
 to set \verb'$GLITE_LOCATION_VAR/purge'.
 
 When export to Job Provenance is enabled (Sect.~\ref{run:purge})
-job registrations are exported to \verb'/tmp/jpreg_'
+job registrations are exported to directory \verb'/tmp/jpreg'
 overridden in startup script with \verb'--jpreg-dir' to \verb'$GLITE_LOCATION_VAR/jpreg'.
 In addition, dump files are further processed in \verb'GLITE_LOCATION_VAR/jpdump'.