I have reformulated my original question in the form of 3 new small sh scripts to illustrate exactly what I am struggling with, w.r.t parent/child process behavior:

Consider a "parent" process:

Code:

#!/bin/sh

sleep 600 &
#./child1 &
PID1="$!"

sleep 600 &
#./child2 &
PID2="$!"

trap "kill $PID1 $PID2" exit  INT
wait

I made the script executable with ">chmod "+x" parent" and executed it in a bash environment, via ">./parent".

I then do a "ps -alf | grep dludick" to see my list of running processes, I observe the following output:
The parent process and the 2 sleep (children) are clearly running.

When I then execute a ">kill -s SIGINT 22421" all the processes are killed correctly. I verify this by doing a "ps -alf | grep dludick" and observe:
Now, when I change the parent script to:

Code:

#!/bin/sh

#sleep 600 &
./child1 &
PID1="$!"

#sleep 600 &
./child2 &
PID2="$!"

trap "kill $PID1 $PID2" exit  INT
wait

where the child1 and child2 scripts are as follow

child1:

Code:

#!/bin/sh
echo starting proc 1, pid=$$
sleep 600

and child2:

Code:

#!/bin/sh
echo starting proc 2, pid=$$
sleep 600

(Note that each for each of the above scripts you also need to do ">chmod "+x" child1/2"

When again executing the parent via ">./parent" followed by ">ps -alf | grep dludick" I get the following active process summary:

Illustrating the correct "parent/child" relationships.

Now, when I kill the parent with a SIGINT ("> kill -s SIGINT 22469") I see that the following processes remain active:
Does anybody know why the sleep processes are not being killed when each of the children receives a "SIGINT" signal? How can I modify the above scripts to ensure this?