In the npm-qnet-l4_lite.so helpviewer page, under caveats the following
entry can be found:
"
If you use bind=en, you want to use resolve=dns as well.
Don’t use the options bind=en and resolve=dns together; that combination is
invalid.
"
I’ve contorted my brain as hard as I can, but I always get a little 0=1
meltdown.
Robert.
Robert Muil <r.muil@crcmining.com.au> wrote:
In the npm-qnet-l4_lite.so helpviewer page, under caveats the following
entry can be found:"
If you use bind=en, you want to use resolve=dns as well.
Don’t use the options bind=en and resolve=dns together; that combination is
invalid.
"I’ve contorted my brain as hard as I can, but I always get a little 0=1
meltdown.
It’s been fixed for the next release. Here’s what it says now:
If you use the bind=ip option, you also need to use the resolve=dns or
resolve=file option. The resolver is used to map the nodename to the IP
address; you can’t use the default resolver with the bind=ip option.
and:
The combination of bind=en and resolve=dns is invalid.
Steve Reid <stever@sreid.ott.qnx.com> wrote:
It’s been fixed for the next release. Here’s what it says now:
If you use the bind=ip option, you also need to use the resolve=dns or
resolve=file option. The resolver is used to map the nodename to the IP
address; you can’t use the default resolver with the bind=ip option.and:
The combination of bind=en and resolve=dns is invalid.
Too bad the default in 6.3 is to use qnet-l4_lite which only supports bind=en
and not bind=ip. Come to think of it, I don’t think it supports any of the
other QOS options that are also documented for Qnet, namely the ~ extensions
that are used when opening connections/devices/files over Qnet.
Martin Zimmerman camz@passageway.com
Camz Software Enterprises www.passageway.com/camz/qnx/
QNX Programming & Consulting www.qnxzone.com