On 9/4/07, Serge E. Hallyn <serue@xxxxxxxxxx> wrote: > We could of course have the ns_container subsystem do that. The > ns_container generally stick around until the admin does a manual rm on > its directory, so this way we could keep the nsproxy around. So how about taking sys_hijack() even further and integrate it with control groups too? So when you do sys_hijack() (or maybe an alternative name would be sys_fork_in()?) you create a task that inherits all the control groups of the target task, as well as the namespaces. Paul _______________________________________________ Containers mailing list Containers@xxxxxxxxxxxxxxxxxxxxxxxxxx https://lists.linux-foundation.org/mailman/listinfo/containers
