Bug 690637 - inconsistent numbering in replication set up
Summary: inconsistent numbering in replication set up
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Directory Server
Classification: Red Hat
Component: Doc-administration-guide
Version: 9.0
Hardware: Unspecified
OS: Unspecified
high
unspecified
Target Milestone: ---
: ---
Assignee: Deon Ballard
QA Contact: ecs-bugs
URL:
Whiteboard:
Depends On:
Blocks: 434914
TreeView+ depends on / blocked
 
Reported: 2011-03-24 21:26 UTC by Rich Megginson
Modified: 2011-06-16 01:52 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed:
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Rich Megginson 2011-03-24 21:26:49 UTC 
8.4 Configuring Single-Master Replication
"there are two major steps" then it lists 3 steps - should say "there are three major steps"

8.7.4 Configuring Replication Agreements from the Command Line
"has to define seven things" then it has a bullet list with 5 items describing 8 different attributes to define - not sure how to handle this, but we should be numerically consistent
Comment 1 Deon Ballard 2011-05-02 18:54:01 UTC 
First one is done:

http://documentation-stage.bne.redhat.com/docs/en-US/Red_Hat_Directory_Server/9.0/html/Administration_Guide/Managing_Replication-Configuring_Single_Master_Replication.html

For the second one, I tried to rephrase it a bit, but I like having some of the attributes given in the same bullet point since they work as a pair. See if this is better:

http://documentation-stage.bne.redhat.com/docs/en-US/Red_Hat_Directory_Server/9.0/html/Administration_Guide/Managing_Replication-Configuring-Replication-cmd.html#Configuring-Replication-ReplAgmt-cmd
Comment 2 Deon Ballard 2011-05-02 18:54:22 UTC 
Oh, these same changes are in the 8.2 docs, too.
Comment 3 Deon Ballard 2011-05-19 18:05:55 UTC 
Setting MODIFIED bugs to ON_QA.
Note You need to log in before you can comment on or make changes to this bug.