svn commit - mysqldoc@docsrva: r2198 - trunk/refman-5.1

[jon]

Author: jstephens
Date: 2006-05-25 12:01:12 +0200 (Thu, 25 May 2006)
New Revision: 2198

Log:

Reformat



Modified:
   trunk/refman-5.1/events.xml

Modified: trunk/refman-5.1/events.xml
===================================================================
--- trunk/refman-5.1/events.xml	2006-05-25 09:56:24 UTC (rev 2197)
+++ trunk/refman-5.1/events.xml	2006-05-25 10:01:12 UTC (rev 2198)
@@ -199,14 +199,14 @@
       </listitem>
 
     </itemizedlist>
-    
+
     <para>
       Events are executed by a special <firstterm>event scheduler
-        thread</firstterm>; when we refer to the Event Scheduler, we
+      thread</firstterm>; when we refer to the Event Scheduler, we
       actually refer to this thread. When running, the event scheduler
       thread and its current state can be seen by users having the
       <literal>SUPER</literal> privilege in the output of <literal>SHOW
-        PROCESSLIST</literal>, as shown in the discussion that follows.
+      PROCESSLIST</literal>, as shown in the discussion that follows.
     </para>
 
     <para>
@@ -215,8 +215,9 @@
       with MySQL 5.1.11, it can have one of these 3 values, which affect
       event scheduling as follows:
     </para>
-    
+
     <itemizedlist>
+
       <listitem>
         <para>
           <literal>0</literal>: Event scheduling is OFF: The event
@@ -226,27 +227,27 @@
           instead, to turn off event scheduling altogether, you must
           start the server with
           <literal><option>--event-scheduler</option>=0</literal>
or
-         
<literal><option>--event-scheduler</option>=OFF</literal>. 
+         
<literal><option>--event-scheduler</option>=OFF</literal>.
         </para>
-        
+
         <para>
           When the Event Scheduler is turned OFF, the event scheduler
           thread does not run, and so cannot be seen listed in the
           output of <literal>SHOW PROCESSLIST</literal>.
         </para>
       </listitem>
-      
+
       <listitem>
         <para>
           <literal>1</literal>: The Event Scheduler is ON; the event
           scheduler thread runs and executes all scheduled events.
         </para>
-        
+
         <para>
           When the Event Scheduler is in the ON state, it will appear to
           be sleeping:
         </para>
-        
+
 <programlisting>
 mysql&gt; <userinput>SHOW PROCESSLIST\G</userinput>
 *************************** 1. row ***************************
@@ -270,7 +271,7 @@
 2 rows in set (0.00 sec)
 </programlisting>
       </listitem>
-      
+
       <listitem>
         <para>
           <literal>2</literal>: The Event Scheduler is SUSPENDED; the
@@ -278,13 +279,13 @@
           scheduled events. This is the default value for
           <literal>event_scheduler</literal>.
         </para>
-        
+
         <para>
           When the Event Scheduler is in the SUSPENDED state, this can
           be seen from the <literal>State</literal> column in the output
           of <literal>SHOW PROCESSLIST</literal> as shown here:
         </para>
-        
+
 <programlisting>
 mysql&gt; <userinput>SHOW PROCESSLIST\G</userinput>
 *************************** 1. row ***************************
@@ -307,10 +308,10 @@
    Info: SHOW PROCESSLIST
 2 rows in set (0.00 sec)
 </programlisting>
-      </listitem>      
+      </listitem>
 
     </itemizedlist>
-    
+
     <para>
       Provided that the event scheduler thread has not been deactivated
       by starting the server with <option>--event-scheduler=0</option>,
@@ -329,7 +330,7 @@
 <programlisting>
 SET @@global.event_scheduler = 1;
 </programlisting>
-    
+
     <para>
       If event scheduling is enabled, you can suspend it by issuing
       either one of these two statements:
@@ -346,24 +347,24 @@
 <programlisting>
 SET @@global.event_scheduler = 2;
 </programlisting>
-        
+
     <para>
-      <emphasis role="bold">Important</emphasis>: Once the server
-      has been started with the event scheduler thread deactivated,
-      the thread cannot be activated &mdash; that is, if the server
-      was started with <option>--event-scheduler=0</option>, then
-      <literal>event_scheduler</literal> cannot be set to 
+      <emphasis role="bold">Important</emphasis>: Once the server has
+      been started with the event scheduler thread deactivated, the
+      thread cannot be activated &mdash; that is, if the server was
+      started with <option>--event-scheduler=0</option>, then
+      <literal>event_scheduler</literal> cannot be set to
       <literal>1</literal> or <literal>2</literal> &mdash;
without
-      restarting <command>mysqld</command>. Similarly, if the server
-      was started with the event scheduler thread running &mdash;
-      that is, with <option>--event-scheduler=1</option> or
+      restarting <command>mysqld</command>. Similarly, if the server was
+      started with the event scheduler thread running &mdash; that is,
+      with <option>--event-scheduler=1</option> or
       <option>--event-schedule=2</option> &mdash; you cannot stop the
       event scheduler thread by issuing <literal>SET
-        @@global.event_scheduler = 0;</literal>. Attempting to start or
+      @@global.event_scheduler = 0;</literal>. Attempting to start or
       stop the event scheduler thread while the server is running causes
-      an error, as shown here: 
+      an error, as shown here:
     </para>
-    
+
 <programlisting>
 mysql&gt; <userinput>SELECT @@global.event_scheduler;</userinput>
 +--------------------------+
@@ -383,7 +384,7 @@
       Since <literal>event_scheduler</literal> is a global variable, you
       must have the <literal>SUPER</literal> privilege to set its value.
     </para>
-    
+
     <para>
       The event scheduler thread cannot be killed. If you attempt to
       <literal>KILL</literal> the event scheduler thread, the effect is
@@ -405,7 +406,7 @@
       scheduler thread executes all events whose scheduling conditions
       are satisfied.
     </para>
-    
+
     <para>
       <emphasis role="bold">Note</emphasis>: Prior to MySQL 5.1.11,
       <literal>event_scheduler</literal> could take one of only the 2