system not startup up via postConfigure/startsSystem - remote_command issue

Customer had an issue with a a multi-node system not starting up either via postConfigure or mcsadmin startsystem.

We was able to reproduce the issue and the problem was that a banner is used at ssh login time that has "#" in it and the 1.0.9 version of remote_command.sh watches for "#" as an indication that the command has finished. So this cause the command that was being passed by the remote_command script not to run.

This issue has been fixed in the 1.1.0 version of remote_command.sh, so that fixes needs to be back ported to 1.0.10.

Work-around is the commit out these lines in the remote_command.sh script to get things to work:

grep "#" remote_command.sh

#expect -re

{[$#] }
# -re {[$#] }

{ exit 0 }
# -re {[$#] } { exit 0 }

1. expect -re {[$#] }
   { exit 0 }

also this needs to be setup in /etc/ssh/sshd_config

1. no default banner path
2. Banner /etc/issue

and this needs to be in the banner file, example like this:

###############################