Bug 840083 - Ensure that device parameters are documented for each configuration file section in which they are supported
Ensure that device parameters are documented for each configuration file sect...
Status: CLOSED CURRENTRELEASE
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: doc-DM_Multipath (Show other bugs)
6.4
Unspecified Unspecified
unspecified Severity unspecified
: rc
: ---
Assigned To: Steven J. Levine
ecs-bugs
: Documentation
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2012-07-13 12:04 EDT by Steven J. Levine
Modified: 2012-09-27 13:34 EDT (History)
4 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2012-09-27 13:32:05 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Steven J. Levine 2012-07-13 12:04:48 EDT
For RHEL 6.3, support for some configuration file parameters was added to the devices section of the multipath.conf file. Check against this info to be sure we have it all correct in the latest document (info received from Ben Marzinski):

> user_friendly_names:
> configurable in multipaths section for 6.3?
yes
> configurable in devices section for 6.3?
yes

> flush_on_last_del
> configurable in multipaths section for 6.3?
yes
> configurable in devices section for 6.3?
yes

> max_fds
> configurable in multipaths section for 6.3?
no
> configurable in devices section for 6.3?
no

> queue_without_daemon
> configurable in multipaths section for 6.3?
no
> configurable in devices section for 6.3?
no
Comment 1 Steven J. Levine 2012-09-27 13:32:05 EDT
All of these defaults are documented in the appropriate tables, so there are not fixes here. Closing this bug.
Comment 2 Steven J. Levine 2012-09-27 13:34:34 EDT
Changing status to closed current release -- it was a bug, but it's already in the published document, so that seems a better fit.

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