[DRBD-cvs] documentation by lars; add some missing </para> tags

[drbd-user@lists.linbit.com]

DRBD CVS committal

Author  : lars
Project : drbd
Module  : documentation

Dir     : drbd/documentation


Modified Files:
      Tag: rel-0_7-branch
	drbd.conf.sgml 


Log Message:
add some missing </para> tags
===================================================================
RCS file: /var/lib/cvs/drbd/drbd/documentation/drbd.conf.sgml,v
retrieving revision 1.9.2.5
retrieving revision 1.9.2.6
diff -u -3 -r1.9.2.5 -r1.9.2.6
--- drbd.conf.sgml	8 Jul 2004 09:53:43 -0000	1.9.2.5
+++ drbd.conf.sgml	9 Jul 2004 18:13:09 -0000	1.9.2.6
@@ -376,7 +376,7 @@
 of a second, the partner node
 is considered dead and therefore the TCP/IP connection is abandoned. This must be lower than <replaceable>connect-int</replaceable> and <replaceable>ping-int</replaceable>.
 The default value is 60 = 6 seconds, the unit 0.1 seconds.
-  </listitem>
+  </para></listitem>
 </varlistentry>
 
 <varlistentry>
@@ -385,7 +385,7 @@
 In case it is not possible to connect to the remote DRBD device immediately,
 DRBD keeps on trying to connect. With this option you can set the time
 between two tries. The default value is 10 seconds, the unit is 1 second.
-  </listitem>
+  </para></listitem>
 </varlistentry>
 
 <varlistentry>
@@ -395,7 +395,7 @@
 <replaceable>time</replaceable> seconds, DRBD will generate a keep-alive
 packet to check if its partner is still alive. The default is 10 seconds,
 the unit is 1 second.
-  </listitem>
+  </para></listitem>
 </varlistentry>
 
 <varlistentry>
@@ -407,7 +407,7 @@
   For hight performance installations it might help, if you
   increase that number. These buffers are used to hold
   datablocks while they are written to disk.
-  </listitem>
+  </para></listitem>
 </varlistentry>
 
 <varlistentry>
@@ -415,7 +415,7 @@
   <listitem><para>
   The highest number of data blocks between two write barriers.
   If you set this smaller than 10 you might decrease your performance.
-  </listitem>
+  </para></listitem>
 </varlistentry>
 
 <varlistentry>
@@ -426,7 +426,7 @@
 <replaceable>timeout</replaceable>, it is expelled from the cluster.
 (I.e. the primary node goes into StandAlone mode.)
 The default is 0, which disables this feature.
-  </listitem>
+  </para></listitem>
 </varlistentry>
 
 <varlistentry>
@@ -458,7 +458,7 @@
   Always use a negative value, positive will (try to) force primary status,
   which is not what you want, if it has outdated data.
   Default is 0, which means unlimited. Unit is seconds.
-  </listitem>
+  </para></listitem>
 </varlistentry>
 
 <varlistentry>
@@ -491,7 +491,7 @@
   that devices which lower devices share one and the same
   physical disk sync in parallel. The default group is 0. I.e. per
   default all devices sync parallel. Negative and positive numbers are allowed.
-  </listitem>
+  </para></listitem>
 </varlistentry>
 
 <varlistentry>