From 382dfebb79b6067198700393c24969121db9ba25 Mon Sep 17 00:00:00 2001
From: Mark Craig <mark.craig@forgerock.com>
Date: Fri, 06 Sep 2013 07:29:01 +0000
Subject: [PATCH] Clarify what it means to defer upgrade tasks
---
opends/src/main/docbkx/install-guide/chap-upgrade.xml | 9 +++++++--
1 files changed, 7 insertions(+), 2 deletions(-)
diff --git a/opends/src/main/docbkx/install-guide/chap-upgrade.xml b/opends/src/main/docbkx/install-guide/chap-upgrade.xml
index 7a0c6f1..31c0416 100644
--- a/opends/src/main/docbkx/install-guide/chap-upgrade.xml
+++ b/opends/src/main/docbkx/install-guide/chap-upgrade.xml
@@ -113,8 +113,13 @@
script files that you copied over the current server files.</para>
<para>By default, the <command>upgrade</command> command requests
- confirmation before making important configuration changes. You can use
- the <option>--no-prompt</option> option to run the command
+ confirmation before making important configuration changes. For some
+ potentially long-duration tasks, such as rebuilding indexes, the default
+ choice is to defer the tasks until after upgrade. Tasks that are not
+ performed during upgrade must generally be performed after upgrade but
+ before you restart the server.</para>
+
+ <para>You can use the <option>--no-prompt</option> option to run the command
non-interactively, with the <option>--acceptLicense</option> option to
accept the license terms non-interactively.</para>
--
Gitblit v1.10.0