OpenVZ Forum


Home » Mailing lists » Devel » namespace and nsproxy syscalls
Re: namespace and nsproxy syscalls [message #16729 is a reply to message #16725] Tue, 03 October 2006 14:43 Go to previous messageGo to previous message
serue is currently offline  serue
Messages: 750
Registered: February 2006
Senior Member
Quoting Herbert Poetzl (herbert@13thfloor.at):
> > > how to avoid having duplicate identifiers when there
> > > is a chance that the same pid will be used again
> > > to create a second namespace?
> > 
> > Well at least that's simple, the pid will no longer be a valid handle to
> > the first namespace ever since that process died  :)
> 
> which simply makes it inaccesible which is not
> what you actually want, sorry ...

Nonsense.  It is still accessible via any other pids for processes in
that namespace.  (i.e. if you're in pidns 1, and (pidns 2, pid 1)
has started (pidns 2, pid 2) and then exited, then (pidns 2, pid 2)
will also be known by some (pidns 1, pid X), so you can access the
namespace via pid X from your pidns 1 process.

How to actually find a pid that will last long enough for you to find
it and then access it is an exercise left to the reader  :)

In other words, I was saying that the duplicate identifiers is not a
bug, but I thought I had left it clearly implied that the approach not
practical, and we will need namespace ids.

-serge
_______________________________________________
Containers mailing list
Containers@lists.osdl.org
https://lists.osdl.org/mailman/listinfo/containers
 
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Previous Topic: megaraid question
Next Topic: [PATCH 2.6.18] ext3: errors behaviour fix
Goto Forum:
  


Current Time: Sat Jul 26 13:13:30 GMT 2025

Total time taken to generate the page: 0.28690 seconds