> -----Original Message-----
> From: Xiaodan Tang [mailto:community-noreply@qnx.com]
> Sent: April-06-09 4:53 PM
> To: technology-networking
> Subject: RE: pid/nid from name
> 
> There is GNS! :)
> 
> The nid always valid to whoever is looking at it.
> 
> If on node A, you have a name. AND, from same node, you do "ls", you
> should see nid = 0; but if you goes to node B, and do "ls
> /net/nodeA/dev/name/...", you see a nid which won't be 0 (nodeA'd nid
> on
> B).
> 
> Not sure this is clear enough. :)

Yes but this not what I'm seing.

Node A (called neutrino) runs gns -s, node B runs gns -c.  I start the application on node A and it creates "/dev/name/
global/mcharest/logc/Trace_0"

ls -l gives me "lr-xr-xr-x  0 root      root              0 Apr 07 09:01 0,172687673,2,0,12 -> ../../../net/neutrino.
comact.com/ /mcharest/logc/Trace_0/0,172687673,2,0,12"

Node is 0 hence everything look ok .  Then I go on Node B.

ls -l /dev/name/global/mcharest/logc/Trace_0 returns:

lr-xr-xr-x  0 root      root              0 Apr 07 13:01 0,172687673,2,0,12 -> ./../../net/neutrino.comact.com/mcharest/
logc/Trace_0/0,172687673,2,0,12

See, the node number is still 0.  If I do like in your example, from node B I do ls -l /net/neutrino/dev/name/global/
mcharest/logc/Trace_0 I still get a 0.  Even if that method would work it's the chicken & egg problem.

> 
> Anyway, which ever machine you are on, you should always be able to
> ConnectAttach(nid, pid, chid, ..) that returns back to you.
> 
> -xtang
> 
> > -----Original Message-----
> > From: Mario Charest [mailto:community-noreply@qnx.com]
> > Sent: April 6, 2009 4:47 PM
> > To: technology-networking
> > Subject: RE: pid/nid from name
> >
> > > -----Original Message-----
> > > From: Xiaodan Tang [mailto:community-noreply@qnx.com]
> > > Sent: April-06-09 4:39 PM
> > > To: technology-networking
> > > Subject: RE: pid/nid from name
> > >
> > > Try the back door then :)
> > >
> > >
> /proc/mount/dev/name/[global|local]/<your_registered_name>/<node>,<pid>
> > > ,
> > > <chid>,<ftype>,<handle>
> >
> > There doesn't seem to be anything under /proc/mount/dev/name/global
> but
> > the info on gns
> >
> > I tried it  under /dev/name/global, but the <node> field can be 0 in
> some
> > cases depending on the relationship between the location of the
> program
> > and the location of the gns server, at least that is what I observed.
> >
> > >
> > > -xtang
> > >
> > >
> > > > -----Original Message-----
> > > > From: Mario Charest [mailto:community-noreply@qnx.com]
> > > > Sent: April 6, 2009 4:35 PM
> > > > To: technology-networking
> > > > Subject: RE: pid/nid from name
> > > >
> > > > Hum not sure, the idea is it's possible the process is stuck in a
> > > loop,
> > > > it's my understanding that a name_open() will not work, since it
> > > wouldn't
> > > > be able to handle the IO_CONNECT  message.  My goal is to kill
> > > (SIGKILL)
> > > > processes that haven't respond to our normal termination method,
> I
> > > cannot
> > > > assume they are in a sane state.
> > > >
> > > > > -----Original Message-----
> > > > > From: Colin Burgess [mailto:community-noreply@qnx.com]
> > > > > Sent: April-06-09 4:23 PM
> > > > > To: technology-networking
> > > > > Subject: Re: pid/nid from name
> > > > >
> > >...