Hi!

I'm running my tests on a xScale PXA255 with QNX 6.3.2 and io-net base network stack.

# pidin info
CPU:ARM Release:6.3.2  FreeMem:15Mb/64Mb BootTime:Jan 01 00:00:00 UTC 1970
Processor1: 1761946886 pxa250 399MHz
# pidin arg
     pid Arguments
       1 procnto
       2 slogger
...
   69641 io-net -dsmc9000 ioport=0x04000300,speed=10,duplex=1,irq=130,variant=generic,width=32 -ptcpip
   81931 pipe
  155661 inetd
...
  356413 fs-cifs //AG /HOST temp
  438331 pidin arg
# cat /etc/hosts
192.168.X.Y2 ag.pc.net.intra ag
192.168.X.Y9 dim.c3.net.intra dim
192.168.X.Y8 pam.c3.net.intra pam
192.168.X.Y9 dem.c3.net.intra dem
# setconf _CS_DOMAIN "c3.net.intra"
# setconf _CS_HOSTNAME "dim"
# sloginfo
Time             Sev Major Minor Args
...
Mar 19 10:37:26    5     8     0 Attached /dev/io-graphics/crt00, id = 3
# ls -l /lib/libsocket*
-rwxrwxrwx  1 root      0            160709 May 05  2004 /lib/libsocket.so.2
#

!!!! Now I'll mount QNET without libsocket.so... !!!!
# mount -Tio-net -obind=ip,resolve=dns /H*/npm-qnet.so
# ls /net
# ls /net/dim
ls: No route to host (/net/dim)
# ls /net/pam
ls: No route to host (/net/pam)
# sloginfo
Time             Sev Major Minor Args
...
Mar 19 10:37:26    5     8     0 Attached /dev/io-graphics/crt00, id = 3
Mar 19 10:41:51    7    15     0 npm-qnet(L4): qnet_birth(): qnet_init() - calling

Mar 19 10:41:51    7    15     0 npm-qnet(L4): ip_ionet_rx_ctrl(): _IO_NET_MSG_DL_ADVERT: new interface: ip0: index 0 
cell 1 endpt 0 iface 2

Mar 19 10:41:51    7    15     0 npm-qnet(L4): ip_ionet_rx_ctrl(): _IO_NET_MSG_ADDR_ADD: no existing interface for 
ND_LOCAL_NODE

Mar 19 10:41:51    7    15     0 npm-qnet(L4): ip_ionet_rx_ctrl(): _IO_NET_MSG_ADDR_ADD: ndb_query_add_name(dim.c3.net.
intra) returned 309

Mar 19 10:41:51    7    15     0 npm-qnet(L4): qnet_birth(): qnet_init() - complete: 0

#

That's it. ;-)

It looks like npm-qnet.so tried to mount libsocket.so to get gethostbyname() from there... but... 

--
AG

> What type of CPU architecture was this on?  I was trying it on my x86 box
> and couldn't seem to reproduce it...
> 
> Does sloginfo report anything interesting in the failed case?
> 
> 	Robert.
> 
> -----Original Message-----
> From: Andrew Golovnia [mailto:andrew_golovnia@ukr.net] 
> Sent: Monday, March 17, 2008 1:53 PM
> To: general-networking
> Subject: QNET and libsocket.so
> 
> Hi!
> 
> I found strange issue with Qnet over IP and I think this thing must be shown
> in documentation or fixed in code.
> If in your target FS not present libsocket.so (not libsocket.so.2 but
> without .2) than Qnet over IP mount npm-qnet-l4_lite.so but Qnet doesn't
> work.
> 
> So I had libsocket.so.2 but no libsocket.so in my target FS and all
> application which uses tcp/ip sockets work fine except Qnet over IP. So Qnet
> need exactly libsocket.so (as for example symbolic link).
> 
> I found no any word about this issue in current documentation.
> 
> Thanks!
> --
> AG
>