From 4bacff33d56b17ab19a5c7dfa40dac52b987ec9d Mon Sep 17 00:00:00 2001 From: =?utf8?q?Ale=C5=A1=20K=C5=99enek?= Date: Thu, 9 Oct 2008 10:58:29 +0000 Subject: [PATCH] make it build --- org.glite.lb.doc/src/LBAG-Installation.tex | 6 +++--- org.glite.lb.doc/src/LBAG-Running.tex | 1 + 2 files changed, 4 insertions(+), 3 deletions(-) diff --git a/org.glite.lb.doc/src/LBAG-Installation.tex b/org.glite.lb.doc/src/LBAG-Installation.tex index f897d2a..5d4752f 100644 --- a/org.glite.lb.doc/src/LBAG-Installation.tex +++ b/org.glite.lb.doc/src/LBAG-Installation.tex @@ -134,14 +134,14 @@ space. There were two such notable upgrades: \begin{itemize} -\item Version 1.4.3 of \textt{glite-lb-server} package. This \LB server version introduced optional use of database transactions for \LB database updates in order to improve their performace. This feature is switched on by default when underlaying MySQL database uses transactional InnoDB tables. For new installations, YAIM configuration process will create transactional database automatically. Existing databases can be converted using provided SQL command script: +\item Version 1.4.3 of \texttt{glite-lb-server} package. This \LB server version introduced optional use of database transactions for \LB database updates in order to improve their performace. This feature is switched on by default when underlaying MySQL database uses transactional InnoDB tables. For new installations, YAIM configuration process will create transactional database automatically. Existing databases can be converted using provided SQL command script: \begin{quote} \verb'mysql -u lbserver lbserver20