Xiaodan Tang(deleted)
|
RE: RE: Disabling QNET comms on a single interface
|
Xiaodan Tang(deleted)
09/30/2009 10:18 AM
post39075
|
RE: RE: Disabling QNET comms on a single interface
Okay, if you are mounting qnet later, you should use command line like
this:
# mount -Tio-pkt -o bind=en0 lsm-qnet.so
Also, please double check "en0" is the interface you want QNET running
on, depends on how you setup the vmware, it might in a different name.
-xtang
> -----Original Message-----
> From: Daniel Fearon [mailto:community-noreply@qnx.com]
> Sent: September 30, 2009 10:16 AM
> To: general-community
> Subject: Re: RE: Disabling QNET comms on a single interface
>
> Thank you for your response, which I've attempted to follow. So far,
I've
> been unsuccessful in getting Qnet to bind to the en0 interface.
>
> Below is a run down of the steps I took to achieve this:
>
> # cd /usr/qnx641/target/qnx6/x86/boot/build/
> # vi qnxbasesmp.build
>
> Change the existing entry below to what you have suggested (further
below):
>
> "mount -Tio-pkt lsm-qnet.so"
> becomes... "mount -Tio-pkt -p bind=en0 lsm-qnet.so"
> (note - i have tried -p bind=en0 before and after lsm-qnet.so)
>
> Write changes to the file and then create a new ifs image, which is
loaded
> on the next startup:
> # mkifs qnxbasesmp.build /.boot/qnxbasesmp.ifs
>
>
> Can you confirm that I'm using the correct parameters you have
suggested,
> and if this is the correct location to be calling them? I think it's
quite
> close and sounds like a very plausible solution, so any further
assistance
> to get there would be greatly appreciated.
>
>
> Thanks,
> Danny
>
>
>
> _______________________________________________
>
> General
> http://community.qnx.com/sf/go/post39074
|
|
|