I found out a little controversy case in regard of multiple io-net
instances.
http://www.qnx.com/developer/docs/momentics_nc_docs/neutrino/sys_arch/tcpip.
html#MULTISTACK states “You can even run multiple, independent instances of
the network manager (io-net) itself. As with all QNX system components, each
io-net naturally benefits from complete memory protection thanks to QNX’s
microkernel architecture.”
http://www.qnx.com/developer/docs/momentics_nc_docs/neutrino/utilities/i/io-
net.html is more rigorous: “Don’t try to start more than one instance of
io-net.”
Dmitri Poustovalov <pdmitri@bigfoot.com> wrote:
: I found out a little controversy case in regard of multiple io-net
: instances.
: http://www.qnx.com/developer/docs/momentics_nc_docs/neutrino/sys_arch/tcpip.
: html#MULTISTACK states “You can even run multiple, independent instances of
: the network manager (io-net) itself. As with all QNX system components, each
: io-net naturally benefits from complete memory protection thanks to QNX’s
: microkernel architecture.”
: http://www.qnx.com/developer/docs/momentics_nc_docs/neutrino/utilities/i/io-
: net.html is more rigorous: “Don’t try to start more than one instance of
: io-net.”
I’ve checked, and you can now run more than one io-net if you’re careful.
In the QNX Momentics Networking Edition, io-net supports new “-i” and “prefix”
options that tell it to register a second pathname. The documentation for
the Networking Edition describes these options in more detail.
We’ll update the Utilities Reference when these options are supported in the
other Momentics editions.
(Note that the System Architecture guide looks ahead, and might describe
features that aren’t fully implemented yet. The other books reflect what’s
currently supported.)
Steve Reid stever@qnx.com
TechPubs (Technical Publications)
QNX Software Systems