qnet question

QNX Newsgroups (Archives) qdn.public.qnxrtp.os
#1

I am using the latest version of QNX (6.1) with patch A on two machines on
the same LAN. I would like to be able to run programs on remote nodes.

From some research in deja.com I found that the way to start qnet is to add
the line:

mount -Tio-net /lib/dll/npm-qnet.so

to the file /etc/rc.d/rc.local and make it executable. I rebooted both
machines after doing this and both give the error message:

mount: Can’t mount / (type io-net)
mount: Possible reason: Resource busy

What has gone wrong?

When the boot process completes I can see the other node in /net and with
sin net (what do the numbers in the sin net output represent?) and I can
copy files between nodes so the network is definately fine.

I then tried to execute a command on a remote node using:

on -d -n NODENAME ls

but the output is just the same as a plain ls command, i.e. it executes on
the host not remote node. Can someone with some experience with qnet tell
me what I’m doing wrong/not doing.

Thanks.

\

Paul.

#2

“Paul Jones” <paul.jones@bnc.ox.ac.uk> wrote in message
news:9tu4v5$sc2$1@inn.qnx.com…

I am using the latest version of QNX (6.1) with patch A on two machines on
the same LAN. I would like to be able to run programs on remote nodes.

From some research in deja.com I found that the way to start qnet is to
add
the line:

mount -Tio-net /lib/dll/npm-qnet.so

to the file /etc/rc.d/rc.local and make it executable. I rebooted both
machines after doing this and both give the error message:

mount: Can’t mount / (type io-net)
mount: Possible reason: Resource busy

What has gone wrong?

With QNX 6.1 qnet is started automaticly. Check for the presence
of /dev/io-net/qnet0" to confirm this.

When the boot process completes I can see the other node in /net and with
sin net (what do the numbers in the sin net output represent?) and I can
copy files between nodes so the network is definately fine.

That proves qnet is started

I then tried to execute a command on a remote node using:

on -d -n NODENAME ls

but the output is just the same as a plain ls command, i.e. it executes on
the host not remote node. Can someone with some experience with qnet tell
me what I’m doing wrong/not doing.

That’s all perfectly normal. ls got executed on the remote node but still
show
the content of the current directory which is the local node. ls has the
environment
of your local node.



Thanks.

\

Paul.