Red Hat Bugzilla – Bug 191899
FENCED_START_TIMEOUT usage in /etc/init.d/fenced
Last modified: 2009-04-16 16:11:38 EDT
if you look at following snippet from /etc/init.d/fenced:
[ -f /etc/sysconfig/cluster ] && . /etc/sysconfig/cluster
# FENCED_START_TIMEOUT -- amount of time to wait for starting fenced
# before giving up. If FENCED_START_TIMEOUT is positive, then we will
# wait FENCED_START_TIMEOUT seconds before giving up and failing when
# fenced does not start. If FENCED_START_TIMEOUT is zero, then
# wait indefinately for fenced to start.
first script sources /etc/sysconfig/cluster and then assigns FENCED_START_TIMEOUT.
So to change FENCED_START_TIMEOUT you need to change script.
It is better first assign FENCED_START_TIMEOUT to default value
and then source /etc/sysconfig/cluster
Addressed in HEAD as well as RHEL4 branch.
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 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.