sin gnames bug in 4.23?

QNX Newsgroups (Archives) qdn.public.qnx4
1

Whenever we run sin gnames it doesn’t get all the global names if there are
heaps of them on the network. Is this a bug, a buffer overrun or a
configurable parameter somewhere? Is there a fix we can download?

Thanks in advance!

Ed

2

Hi Ed,

Not sure if it is a bug or not.

But upgrading to QNX 4.25 would be a good place to start. :slight_smile:

Erick.


Ed Wilkinson <edw@mail.acttab.com.au> wrote:

Whenever we run sin gnames it doesn’t get all the global names if there are
heaps of them on the network. Is this a bug, a buffer overrun or a
configurable parameter somewhere? Is there a fix we can download?

Thanks in advance!

Ed

3

Are you running more than one nameloc? Do all the namelocs see all the nodes
on the network? Are the QNX licenses the same on all nodes? How many global
names are you talking about? I believe there is an option to Proc for the
maximum number of names.

Ed Wilkinson <edw@mail.acttab.com.au> wrote in message
news:5363992.9uPGUboISy@mail.acttab.com.au…

Whenever we run sin gnames it doesn’t get all the global names if there
are
heaps of them on the network. Is this a bug, a buffer overrun or a
configurable parameter somewhere? Is there a fix we can download?

Thanks in advance!

Ed

4

Not sure if it is a bug or not.
But upgrading to QNX 4.25 would be a good place to start. > :slight_smile:

Nice idea, unf we’re not quite in the position to do so at the moment.

Anyway, thanks for the thought.

Ed

5

Stephen Thomas wrote:

Are you running more than one nameloc? Do all the namelocs see all the
nodes on the network? Are the QNX licenses the same on all nodes? How many
global names are you talking about? I believe there is an option to Proc
for the maximum number of names.

Thanks for these questions and ideas, all of them good. Unf, we’re already

tried them :frowning: Oh, well, better luck next time …

Ed