Sockets and AF_LOCAL

QNX Newsgroups (Archives) qdn.public.qnxrtp.os
1

Hi! I had two applications communicating through an internal socket created
using AF_LOCAL address family as the domain. It works in my development PC
w/ a full install. On our target w/ a small boot image it fails when trying
to open a socket for listening using AF_LOCAL. If I switch to AF_INET
everything is fine. Am I missing something on my image that is causing
AF_LOCAL to fail?

Thanks!!

  • Ricardo
2

Not sure what version you have, but try to start “pipe” on your target.
See if that helps.

-xtang

Ricardo <ricardo.fsi@attbi.com> wrote in message
news:at3cho$p5i$2@inn.qnx.com…

Hi! I had two applications communicating through an internal socket
created
using AF_LOCAL address family as the domain. It works in my development PC
w/ a full install. On our target w/ a small boot image it fails when
trying
to open a socket for listening using AF_LOCAL. If I switch to AF_INET
everything is fine. Am I missing something on my image that is causing
AF_LOCAL to fail?

Thanks!!

  • Ricardo
3

“Xiaodan Tang” <xtang@qnx.com> wrote in news:at3f5a$9se$1@nntp.qnx.com:

Not sure what version you have, but try to start “pipe” on your
target. See if that helps.

-xtang

Ricardo <> ricardo.fsi@attbi.com> > wrote in message
news:at3cho$p5i$> 2@inn.qnx.com> …
Hi! I had two applications communicating through an internal socket
created
using AF_LOCAL address family as the domain. It works in my
development PC w/ a full install. On our target w/ a small boot image
it fails when
trying
to open a socket for listening using AF_LOCAL. If I switch to AF_INET
everything is fine. Am I missing something on my image that is
causing AF_LOCAL to fail?

Thanks!!

  • Ricardo

Yeah… pipe is running. I’m using QNX 6.2, BTW. I got the applications
connected to each other using AF_INET and working. If I switch of AF_LOCAL
it doesn’t work. AF_LOCAL works on the development machine w/ the full QNX
6.2 install.

  • Ricardo
4

Ricardo <rar@attbi.com> wrote:

“Xiaodan Tang” <> xtang@qnx.com> > wrote in news:at3f5a$9se$> 1@nntp.qnx.com> :

Not sure what version you have, but try to start “pipe” on your
target. See if that helps.

-xtang

Ricardo <> ricardo.fsi@attbi.com> > wrote in message
news:at3cho$p5i$> 2@inn.qnx.com> …
Hi! I had two applications communicating through an internal socket
created
using AF_LOCAL address family as the domain. It works in my
development PC w/ a full install. On our target w/ a small boot image
it fails when
trying
to open a socket for listening using AF_LOCAL. If I switch to AF_INET
everything is fine. Am I missing something on my image that is
causing AF_LOCAL to fail?

Thanks!!

  • Ricardo



    Yeah… pipe is running. I’m using QNX 6.2, BTW. I got the applications
    connected to each other using AF_INET and working. If I switch of AF_LOCAL
    it doesn’t work. AF_LOCAL works on the development machine w/ the full QNX
    6.2 install.

  • Ricardo

What’s the error? AF_LOCAL support is provided by the full stack.

-seanb