<Signed-off By>: Rishikesh K Rajak <[EMAIL PROTECTED]>
---
Index: ltp-full-20071130/testcases/kernel/containers/pidns/README
===================================================================
--- /dev/null 1970-01-01 00:00:00.000000000 +0000
+++ ltp-full-20071130/testcases/kernel/containers/pidns/README 2007-12-27 16:09:47.000000000 +0530
@@ -0,0 +1,17 @@
+PIDNS testcases Overview:
+
+ A pid namespace is a view of particular set of tasks on the system. For processes, a process may have pid 1234 in one namespace, but have pid 1 in another.This allows processes to use process ids which are in use in other pid namespaces, without having to worry about what pids exist in other namespaces.
+
+"A process has a pid in every ancestor pid namespaces up to the initial pid namespace. If process B is in a child namespace relative to process A, then process A will see process B by the pid which is valid in process A's pid namespace."
+
+"Another way of specifying process visibility, then is that process A will see all tasks which have a valid pid in process A's pid namespace."
+
+
+
+Testcases:
+
+1> Check the process id of container after cloning as 1.
+2> After creation of container the PID Namespace of the container should have the parent group id as 1 and also session id as 1.
+3> Create container: pass the parent namespacei id: mount /proc directory: check parent namespace id inside container: if it is exiting then PASS otherwise FAIL.
+
+Check for PIDNS enablement: from 2.6.24 kernel version.
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Ltp-list mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/ltp-list
