Description of problem: The lock_gulmd init.d service script should fail to start if gulm does not find quorom within a set period of time. This timeout period should be configurable so that users can adjust how long to wait before failing. Options should include something along the lines of "wait indefinately", "don't wait" and "wait for X seconds". This is needed in order to prevent services requiring quorom (such as mounting GFS) to hang when quorom is not possible. For example, without this feature, machines disconnected from an ethernet switch will not be able to boot since quorom can never be established. The default timeout will probably be set to 5 minutes. If after the timeout period gulm is still not quorate, it will terminate the localy running lock_gulmd process and report a failure. Version-Release number of selected component (if applicable): GFS-6.0.0-15 and earlier
This has been resolved in version 1.1.2.5 of gulm/init.d/lock_gulmd
An errata 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 the 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. http://rhn.redhat.com/errata/RHBA-2004-659.html