I am defineing my hostname in my boot image with -Ntest1 to
startup-bios. I.E.
startup-bios -Ntest1
Can I define the domain name at this point too?
I have found that io-net seems to come up faster if I specify the
protocols before the device. I.E.
ionet -ptcpip -pqnet -dspeedo
Is there any harm in doing this? The docs say that the device
should come first.
If I type:
ls /net
I can only see myself for a long time.
How can I hasten the discovery of other RTP hosts on the network?
I did notice that if I type:
ls/net/<some_other_node>
it immediately finds it.
If I type:
ls /net
I can only see myself for a long time.
How can I hasten the discovery of other RTP hosts on the network?
I did notice that if I type:
ls/net/<some_other_node
it immediately finds it.
Yeah…there was a good discussion on this sometime ago. It would be nice
if there was some
kind of interrogation, but if I remember correctly this would also cause a
lot of network traffic and could cause undesirable performance in some
cases…but it still would be a nice feature, especially if qnet did no
interrogation until it was explicitly asked to do so.
If I type:
ls /net
I can only see myself for a long time.
How can I hasten the discovery of other RTP hosts on the network?
I did notice that if I type:
ls/net/<some_other_node
it immediately finds it.
KS > Yeah…there was a good discussion on this sometime ago. It would be nice
KS > if there was some
KS > kind of interrogation, but if I remember correctly this would also cause a
KS > lot of network traffic and could cause undesirable performance in some
KS > cases…but it still would be a nice feature, especially if qnet did no
KS > interrogation until it was explicitly asked to do so.
OK. What about the “mount=” option to npm-qnet?
If I believe that there should be a test2, test3 and test4 host out
there, can I attempt to pre-mount them so that if they do exist when
io-net gets loaded then they will be visible in /net?