Questions about Socket process failure: "No License"

Hello,
I have a network of embedded computers from RTP Corp. (RTP6800s)
running 4.24 of QNX. The are supposed be configured by the vendor
with the necessary licenses. But the script that starts the network
makes the call:

license -R1

to refresh the licenses from Node 1. This is odd and I am not sure what
the vendor’s intent is. In our configuration, Node 1 will be a
development QNX PC which will NOT be connected to the network all the
time. So I can’t rely on this command.

With out this line in the script, the licinfo command reports:

tcprt 1/1 1

And when I try to load Socket, it fails with the error message:
“No License”.

Then if I run the ‘license -R1’ command (with Node 1 connected to the
network), licinfo reports:

tcprt 2/6 1 5

And the Socket process loads fine.

Shouldn’t one tcprt license should be sufficient to allow me
to run Socket? Node 1 has the tcptk license as well as a lot
of others. I could copy the licenses from Node 1 onto the RTP6800
computer but it may not be legal and I think I should not have to.

Thank you for any guidance on this. -Shawn

I posted a reply to this in comp.os.qnx.

Bill Caroselli


“Shawn” <smdhome@yahoo.com> wrote in message
news:MPG.15a66672d8cb9d70989680@inn.qnx.com

Hello,
I have a network of embedded computers from RTP Corp. (RTP6800s)
running 4.24 of QNX. The are supposed be configured by the vendor
with the necessary licenses. But the script that starts the network
makes the call:

license -R1

to refresh the licenses from Node 1. This is odd and I am not sure what
the vendor’s intent is. In our configuration, Node 1 will be a
development QNX PC which will NOT be connected to the network all the
time. So I can’t rely on this command.

With out this line in the script, the licinfo command reports:

tcprt 1/1 1

And when I try to load Socket, it fails with the error message:
“No License”.

Then if I run the ‘license -R1’ command (with Node 1 connected to the
network), licinfo reports:

tcprt 2/6 1 5

And the Socket process loads fine.

Shouldn’t one tcprt license should be sufficient to allow me
to run Socket? Node 1 has the tcptk license as well as a lot
of others. I could copy the licenses from Node 1 onto the RTP6800
computer but it may not be legal and I think I should not have to.

Thank you for any guidance on this. -Shawn

Thank you for your answer.

In article <9hi9mb$8bu$1@inn.qnx.com>, BillCaroselli@Q-TPS.com says…

I posted a reply to this in comp.os.qnx.

Bill Caroselli


“Shawn” <> smdhome@yahoo.com> > wrote in message
news:> MPG.15a66672d8cb9d70989680@inn.qnx.com> …
Hello,
I have a network of embedded computers from RTP Corp. (RTP6800s)
running 4.24 of QNX. The are supposed be configured by the vendor
with the necessary licenses. But the script that starts the network
makes the call:

license -R1

to refresh the licenses from Node 1. This is odd and I am not sure what
the vendor’s intent is. In our configuration, Node 1 will be a
development QNX PC which will NOT be connected to the network all the
time. So I can’t rely on this command.

With out this line in the script, the licinfo command reports:

tcprt 1/1 1

And when I try to load Socket, it fails with the error message:
“No License”.

Then if I run the ‘license -R1’ command (with Node 1 connected to the
network), licinfo reports:

tcprt 2/6 1 5

And the Socket process loads fine.

Shouldn’t one tcprt license should be sufficient to allow me
to run Socket? Node 1 has the tcptk license as well as a lot
of others. I could copy the licenses from Node 1 onto the RTP6800
computer but it may not be legal and I think I should not have to.

Thank you for any guidance on this. -Shawn