Red Hat Bugzilla – Bug 471854
[NetApp 5.4 feat] Add an option to specify multipathd verbosity through /etc/multipath.conf
Last modified: 2010-01-11 21:44:52 EST
Description of problem:
There are two different problems.
1) Currently there is no clean way of passing arguments to multipathd
daemon during startup. There should be parameter in /etc/multipatd.conf which will tell multipathd to run in particular verbosity mode.
2)If I start multipathd manually with -v3 verbosity, /etc/init.d/multipathd stop doesn't stop multipathd daemon as it compares exact process names.
Version-Release number of selected component (if applicable):
kernel : 2.6.18-121.el5
Steps to Reproduce:
1.Try to configure verbosity in /etc/multipath.conf.
1.Run multipathd daemon manually with verbosity.
2.Stop multipathd service.
1.You won't be able to configure verbosity in multipath.conf.
2.multipathd daemon will not be stopped.
One should be able to configure verbosity in /etc/multipath.conf. And to support this, /etc/init.d/multipathd script should stop multipathd daemon even if it is started with verbosity parameter.
There is now an option to set the verbosity of multipath and multipathd in /etc/multipath.conf
The -v command line option will override this value.
~~ Attention Partners RHEL 5.4 Partner Alpha Released! ~~
RHEL 5.4 Partner Alpha has been released on partners.redhat.com. There should
be a fix present that addresses this particular request. Please test and report back your results here, at your earliest convenience. Our Public Beta release is just around the corner!
If you encounter any issues, please set the bug back to the ASSIGNED state and
describe the issues you encountered. If you have verified the request functions as expected, please set your Partner ID in the Partner field above to indicate successful test results. Do not flip the bug status to VERIFIED. Further questions can be directed to your Red Hat Partner Manager. Thanks!
I have verified it in RHEL 5.4 Partner Alpha, I could set the verbosity of multipathd in /etc/multipath.conf. Thank you.
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.