Description of problem:

In a clustered environment it is sometimes necessary to influence the start behavior of cman, e.g. reduce the expected votes manually using cman_tool to form a quorate cluster. Therefore a remote access using ssh is necessary. Actually sshd is started after cman, so it is not possible to influence cman startup. Usually I change this manually in the kickstart file for cluster nodes to set the start order number of sshd to the one of cman minus 1.

Actually the following chkconfig orders are implemented:

/etc/init.d/cman:# chkconfig: - 21 79
/etc/init.d/sshd:# chkconfig: 2345 55 25

This should be changed to:

/etc/init.d/cman:# chkconfig: - 21 79
/etc/init.d/sshd:# chkconfig: 2345 20 25

during installation of cman rpm. In a kickstart file I usually do this in this way (perl can be substituted by sed):

cman=`perl -n -e 'print ( $1 - 1 ) if $_  =~ /chkconfig:\s\S+\s(\d+)\s\d+\s/' /etc/init.d/cman`
cman_off=$(expr 100 - $cman )
set $cman
set $cman_off
perl -pi -e "s/chkconfig:\s+(\S+)\s+(\S+)\s+(\S+)/chkconfig: \$1 $cman $cman_off/" /etc/init.d/sshd
chkconfig cman off; chkconfig cman on

I think this would be an improvement and could be implemented per default.


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


How reproducible:

Always.

Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info: