Bug 711868 - We need to explain possible options for autostart and
Summary: We need to explain possible options for autostart and
Keywords:
Status: CLOSED NEXTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: doc-Cluster_Administration
Version: 6.2
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Steven J. Levine
QA Contact: ecs-bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-06-08 19:46 UTC by Chris Feist
Modified: 2011-11-14 20:34 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-11-14 20:34:36 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description Chris Feist 2011-06-08 19:46:45 UTC
Description of problem:
In section "5.9. Adding a Cluster Service to the Cluster" we talk about autostart, we need to specify that setting it to '1' enables it (which is the default).  And setting it to anything else disables it.

Version-Release number of selected component (if applicable):
In RHEL 6.1

This isn't a critical issue, but we'd like to fix it as soon as time is available.

I would make these changes:

autostart — Specifies whether to autostart the service when the cluster starts.

should be changed to something like this:

autostart — Specifies whether to autostart the service when the cluster starts.  (Use '1' to enable, '0' to disable, default is enabled).

Comment 2 Steven J. Levine 2011-06-08 20:30:15 UTC
I'm assigning this to me and dev_acking this because autostart is covered in the Cluster Administration guide.

I'll make a note here to check whether it's covered in the Overview as well, but it's definitely in the Cluster Administration document.

Comment 3 Steven J. Levine 2011-08-15 16:48:53 UTC
I have updated the definition of autostart to this suggestion in both the chapter on ccs and the chapter on using the CLI in my working draft.


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