Bug 676572 - MRG/M UG Persistence Options table --truncate option has not specified default state (but the others in the table)
Summary: MRG/M UG Persistence Options table --truncate option has not specified defau...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise MRG
Classification: Red Hat
Component: Messaging_Programming_Reference
Version: 1.3
Hardware: Unspecified
OS: Unspecified
unspecified
low
Target Milestone: 2.0
: ---
Assignee: Alison Young
QA Contact: ecs-bugs
URL:
Whiteboard:
Depends On: 660526
Blocks: 660531
TreeView+ depends on / blocked
 
Reported: 2011-02-10 09:32 UTC by Frantisek Reznicek
Modified: 2015-11-16 01:13 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-06-24 01:43:24 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description Frantisek Reznicek 2011-02-10 09:32:12 UTC
Description of problem:

As part of bug 627228 the documentation of the broker's --truncate documentation was added.

In the added row to Table 6.1. Persistence Options does not contain the default value of the --truncate parameter.

It is necessary to highlight the default parameter value the same way as the others in the same table 6.1.

from
  --truncate yes|no    If yes, truncates the store, discarding any existing records. If no, preserves any existing stores for recovery.

to 

  --truncate yes|no    If yes, truncates the store, discarding any existing records. If no, preserves any existing stores for recovery. The default is no.



Version-Release number of selected component (if applicable):
Red_Hat_Enterprise_MRG-Messaging_User_Guide-1.3-web-en-US-2-4

How reproducible:
N/A (100%)

Steps to Reproduce:
1. See UG Table 6.1. Persistence Options
  
Actual results:
Table 6.1. Persistence Options does not explicitly show the parameter's default value.

Expected results:
Table 6.1. Persistence Options should show the parameter's default value as the other parameters show their defaults.

Additional info:


Note You need to log in before you can comment on or make changes to this bug.