svn commit: r1397259 - /vcl/site/trunk/content/docs/UpgradePreviousVersions/UpgradeFrom2.2.1to2.3.mdtext

[fa...@apache.org]

Author: fapeeler
Date: Thu Oct 11 19:42:02 2012
New Revision: 1397259

URL: http://svn.apache.org/viewvc?rev=1397259&view=rev
Log:
CMS commit to vcl by fapeeler

Modified:
    vcl/site/trunk/content/docs/UpgradePreviousVersions/UpgradeFrom2.2.1to2.3.mdtext

Modified: vcl/site/trunk/content/docs/UpgradePreviousVersions/UpgradeFrom2.2.1to2.3.mdtext
URL: http://svn.apache.org/viewvc/vcl/site/trunk/content/docs/UpgradePreviousVersions/UpgradeFrom2.2.1to2.3.mdtext?rev=1397259&r1=1397258&r2=1397259&view=diff
==============================================================================
--- vcl/site/trunk/content/docs/UpgradePreviousVersions/UpgradeFrom2.2.1to2.3.mdtext (original)
+++ vcl/site/trunk/content/docs/UpgradePreviousVersions/UpgradeFrom2.2.1to2.3.mdtext Thu Oct 11 19:42:02 2012
@@ -41,9 +41,9 @@ This page provides information on how to
 
 Shutdown the httpd and vcld services
            
-            :::BashLexer
-            service httpd stop or /etc/init.d/httpd stop
-            service vcld stop or /etc/init.d/vcld stop
+        :::BashLexer
+        service httpd stop or /etc/init.d/httpd stop
+        service vcld stop or /etc/init.d/vcld stop
 
 # Create a backup of vcl database #
 
@@ -62,10 +62,9 @@ This step updates the mysql schema.
 
         **Note**: A new resource group is added in update-vcl.sql - **all profiles**. Access to manage the group is added to the VCL->admin node in the privilege tree if that node exists. If not, you will need to add it manually after starting httpd again. To add it manually, pick a node in the privilege tree, scroll to Resources, click Add Resource Group, select serverprofile/all profiles from the drop-down box, check available, administer, manageGroup, and manageMapping, and click Submit New Resource Group.
 
-
 # Update web code #
 
-    This step we will move the 2.2.1 web directory out of the way, so we can copy in the new web code base. After copying in the new code, we will migrate your configuration changes. These instructions assume that you installed the vcl web code at /var/www/html/vcl. If you installed it elsewhere, replace /var/www/html/vcl with your vcl web root.
+This step we will move the 2.2.1 web directory out of the way, so we can copy in the new web code base. After copying in the new code, we will migrate your configuration changes. These instructions assume that you installed the vcl web code at /var/www/html/vcl. If you installed it elsewhere, replace /var/www/html/vcl with your vcl web root.
 
 1. move your old code out of the way