Remote execution question

QNX Newsgroups (Archives) comp.os.qnx
#1

I’d like to run an application on a remote node from our primary
QNX server. The application spawns several processes that make
up the application. One of those processes is a command line
interface…which is where my problem lies.

I successfully started the application on the remote node with:
//3 appname

However, I have no way to enter command-line instructions to the
application’s command line interface. I looked at ‘ditto’ to
connect to the console of the remote app, but don’t know how
to get the command line interface to attach to it. It usually
attaches to the pterm window (if in Phindows).

Ideas?

Thanks,
Barry

#2

Instead of spawning on the node, check out the ‘on’ command.
You can start the application on the remote node on a console on the remote
node,
and then ditto that specific console.

The other option is to ditto a console on the remote node, and use the ditto
to start the application. Then it is definitely running on that console on
that node.

Have you used ‘who -n node’ and ‘ps -n node’ to verify what processes are
running on what consoles on what nodes. Possibly your startup is not giving
the expected results.

-Paul

Barry Robertson <brobertson@SoftwareRemodeling.com> wrote in message
news:399AA83A.8F7879C1@SoftwareRemodeling.com…

I’d like to run an application on a remote node from our primary
QNX server. The application spawns several processes that make
up the application. One of those processes is a command line
interface…which is where my problem lies.

I successfully started the application on the remote node with:
file://3 appname

However, I have no way to enter command-line instructions to the
application’s command line interface. I looked at ‘ditto’ to
connect to the console of the remote app, but don’t know how
to get the command line interface to attach to it. It usually
attaches to the pterm window (if in Phindows).

Ideas?

Thanks,
Barry

#3

Thanks.

The ‘on’ command fits perfectly. "on -n3 -f3 " fixed me right up.

-Barry

Paul Russell wrote:

Instead of spawning on the node, check out the ‘on’ command.
You can start the application on the remote node on a console on the remote
node,
and then ditto that specific console.

The other option is to ditto a console on the remote node, and use the ditto
to start the application. Then it is definitely running on that console on
that node.

Have you used ‘who -n node’ and ‘ps -n node’ to verify what processes are
running on what consoles on what nodes. Possibly your startup is not giving
the expected results.

-Paul

#4

Barry Robertson <brobertson@softwareremodeling.com> wrote:

I’d like to run an application on a remote node from our primary
QNX server. The application spawns several processes that make
up the application. One of those processes is a command line
interface…which is where my problem lies.

I successfully started the application on the remote node with:
//3 appname

Look at “on -f3 appname” to put the application fully rooted on
node 3. Also, look at “on -t” options for attaching the application
to a specific console device on a particular machine, probably
something like “on -f3 -t//3/dev/con1 appname” to run the application
on console 1 of node 3.

-David