Once again,

Connected to someprocess@host3
>type message
> <--- since we are just seeing whether we can connect to this process, we will quit this bye
doing control C

OR

Cannot connect: connection refused


If I was doing this interactively,

I would type

./program process.1@host13

IF process.1 was doing what's it suppose to be doing, i would see

Connected to someprocess@host3
>type message
>

and I can type command and do stuff... and only way to quit out of that is to do control-C
But if you do get above message it means from my host to that process on host3, I am able to communicate and that's what I am trying to find out

If process.1 was not up, than I would see

Cannot connect: connection refused

and it will give me back the prompts.


Please let me know if needs more info..
I am just not sure if sending control c within loop is possible in the script or not