qnx_name_locate

When qnx_name_locate is called for a global name say “/module1” on another
node, it automatically calls qnx_vc_attach. What are the flags set when this
occurs? Currently (using qnx_name_locate) when the process/virtual circuit
dies, the remote vid becomes a zombie process which would lead me to believe
that qnx_name_locate calls qnx_vc_attach with a flag of _VC_AT_REM_ZOMBIE.

Thanks,

Doug

Doug Rixmann <rixmannd@rdsdata.com> wrote in message
news:aopkch$si8$1@inn.qnx.com

When qnx_name_locate is called for a global name say “/module1” on another
node, it automatically calls qnx_vc_attach. What are the flags set when
this
occurs? Currently (using qnx_name_locate) when the process/virtual circuit
dies, the remote vid becomes a zombie process which would lead me to
believe
that qnx_name_locate calls qnx_vc_attach with a flag of _VC_AT_REM_ZOMBIE.

qnx_name_locate() does not set any flags. Are you doing a waitpid or is
anyone requesting process information of that nature to keep the pid/vid
zombified?

-Adam

Doug Rixmann <rixmannd@rdsdata.com> wrote:

When qnx_name_locate is called for a global name say “/module1” on another
node, it automatically calls qnx_vc_attach. What are the flags set when this
occurs? Currently (using qnx_name_locate) when the process/virtual circuit
dies, the remote vid becomes a zombie process which would lead me to believe
that qnx_name_locate calls qnx_vc_attach with a flag of _VC_AT_REM_ZOMBIE.

qnx_name_locate() doesn’t set the _VC_AT_REM_ZOMBIE flag, at least not
at the library level. It sets the (private from vc_msg.h)
_VC_AT_NAME_SPEC flag. I don’t know what that actually does inside
Proc, though.

I just want to get what is happening down correctly…
process1 does a qnx_name_locate() for a global name reg’d by a process
on a remote node
process1 exits
the remote side/half of the vc is still around?

Is that what you are saying?

Or is it:
process1 locates process2 on a remote node
process2 dies
the local side/half of the vc is still around?

-David

QNX Training Services
http://www.qnx.com/support/training/
Please followup in this newsgroup if you have further questions.

I should have ended this one before as well. This thread is a double
posting. I the more recent one I mentioned that I was an idiot. :slight_smile: When I
changed the qnx_vc_poll_parm, that was the only process I changed and
assumed that the zombies were coming from it. The zombies are coming from
another process (see _endthread/_beginthread/qnx_spawn message). As I said
before, this has given me a better understanding of the VC’s and netpoll.

Thanks,

Doug
“David Gibbs” <dagibbs@qnx.com> wrote in message
news:aoprn9$g9v$1@nntp.qnx.com

Doug Rixmann <> rixmannd@rdsdata.com> > wrote:
When qnx_name_locate is called for a global name say “/module1” on
another
node, it automatically calls qnx_vc_attach. What are the flags set when
this
occurs? Currently (using qnx_name_locate) when the process/virtual
circuit
dies, the remote vid becomes a zombie process which would lead me to
believe
that qnx_name_locate calls qnx_vc_attach with a flag of
_VC_AT_REM_ZOMBIE.

qnx_name_locate() doesn’t set the _VC_AT_REM_ZOMBIE flag, at least not
at the library level. It sets the (private from vc_msg.h)
_VC_AT_NAME_SPEC flag. I don’t know what that actually does inside
Proc, though.

I just want to get what is happening down correctly…
process1 does a qnx_name_locate() for a global name reg’d by a process
on a remote node
process1 exits
the remote side/half of the vc is still around?

Is that what you are saying?

Or is it:
process1 locates process2 on a remote node
process2 dies
the local side/half of the vc is still around?

-David

QNX Training Services
http://www.qnx.com/support/training/
Please followup in this newsgroup if you have further questions.