Tty "problem" with execNative

Question

Folks,
we have a "small" problem with the execNative stuff:
We have to automate the installation of a tool, which requires a couple of
manual interventions...
One of that is the restart of some software on a different node, and once
that's done, we need to send a "c" for continue to the original task on the
initial server...
We try to minic that be using expect and the spawn/wait functionality.
The problem seems to be, that the execNative is taking away all tty's, and
that exepct can't then send the signals to the "right" processes...
Here's excerpts from what we try to achieve:
SPS xml code:
               <execNative userToRunAs="root" dir=":[workPath]" timeout="18000">
                    <shell cmd="/bin/ksh -x -c">
                         <![CDATA[                         
# Then we need to start the expect script! (this is our InstallScript.xml installed InstallScript!)
./301_install_pai_base.sh
]]>
                    </shell>
               </execNative>
<!-- This next call restarts the DMGR, because that is needed during the installation on non-DMGR hosts... ;-) -->
               <if>
                    <condition><equals value2=":[hostIsDeploymentManager_]" value1="FALSE"/></condition>
                    <then>
                         <retarget host=":[paiDeploymentManagerHostRef_]">
                              <call blockName="restartDmgr">
<!--
                                   <installedComponent path="@pluginFolder@/sunos/sparc/5.10/3.0.1" name="PAI" />
-->
                                   <installedComponent name="PAI" />
                              </call>
                         </retarget>
                    </then>
               </if>
               <execNative userToRunAs="root" dir=":[workPath]" timeout="18000">
                    <shell cmd="/bin/ksh -x -c">
                         <![CDATA[                         
# Then we need to start the expect script! (this is our InstallScriptPart2.xml installed InstallScriptPart2!)
./301_install_pai_base_part2.sh
]]>
                    </shell>
               </execNative>
The scripts are:
301_install_pai_base.sh:
./install_pai_no_dmgr.exp "$SOLUTION_MODULE" "$PSA_PATH" "$LOG_DIR" "$TMP_PAI_DIR" "$BASE_DIR" > ./install_out.log 2>&1 </dev/null &
echo $! >mysuperduperscriptprocessid
updatelog_file="./install_out.log"
sleep 10
if [ -f "$updatelog_file" ]
then
          while :
          do
          last_lines=`tail -2 "$updatelog_file" 2>/dev/null`
     if echo $last_lines | grep "BUILD FAILED" >/dev/null 2>&1
     then
                    echo "There were failures during install!"
                    kill -TERM $id
                    exit 1
fi
          if echo $last_lines | grep "(c,a)" >/dev/null 2>&1
          then
               # The kill -HUP is handled in the continuation script!
               exit 0
          fi
          sleep 1
          done
fi
301_install_pai_base_part2.sh:
id=`cat mysuperduperscriptprocessid`
rm -f mysuperduperscriptprocessid
     updatelog_file="./install_out.log"
     sleep 10
          while :
          do
          last_lines=`tail -2 "$updatelog_file" 2>/dev/null`
     if echo $last_lines | grep "BUILD FAILED" >/dev/null 2>&1
               then
                    kill -TERM $id
                    exit 1
fi
     if echo $last_lines | grep "BUILD SUCCESSFUL" >/dev/null 2>&1
          then
                    kill -HUP $id
                    exit 0
          fi
          sleep 1
          done
install_pai_no_dmgr.exp:
******************************************************************************#!/usr/local/bin/expect
set timeout 1000000
proc sendCtoContinue {mySpawnID} {
send -i $mySpawnID "c\n"
proc sendAtoContinue {mySpawnID} {
send -i $mySpawnID "a\n"
# send_user "Executing ./installPAI.sh\n"
spawn ./startInstaller.sh -m FULL -i [lrange $argv 0 0] -a [lrange $argv 1 1] -l [lrange $argv 2 2] -t [lrange $argv 3 3] -b [lrange $argv 4 4] -p true
set paiSpawnID $spawn_id
trap {sendCtoContinue $paiSpawnID} SIGHUP
trap {sendAtoContinue $paiSpawnID} SIGTERM
expect "(c,a)"
wait $paiSpawnID
expect "Total time:"
# expect "Install complete"
What we found out is:
a.) We need the redirection of the STDIN/STDOUT/STDERR at the first line:
./install_pai_no_dmgr.exp "$SOLUTION_MODULE" "$PSA_PATH" "$LOG_DIR" "$TMP_PAI_DIR" "$BASE_DIR" > ./install_out.log 2>&1 </dev/null &
b.) The retarget clause/statement is executed!
c.) The "part2" script is started!
d.) The "c" is send! (aka, the kill will be executed!)
e.) The "c" does not reach the correct process, aka: the process started via:
spawn ./startInstaller.sh -m FULL -i [lrange $argv 0 0] -a [lrange $argv 1 1] -l [lrange $argv 2 2] -t [lrange $argv 3 3] -b [lrange $argv 4 4] -p true
Any clues?
Do we need to work out something different for that stuff?
Matthias

Answer 1

I don't think the console font is the problem. I use Lat2-Terminus16 because I read the Beginner's Guide on the wiki while installing the system.
My /etc/vconsole.conf:
KEYMAP=de
FONT=Lat2-Terminus16
showconsolefont even shows me the characters missing in the file names; e.g.: Ö, Ä, Ü