From: Daniel Lezcano Date: Fri, 24 Jul 2009 14:41:27 +0000 (+0200) Subject: fix the document according the current version X-Git-Tag: lxc_0_6_3 X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=c159cb963868d4646cf415abb064d8fd4b6ee848;p=thirdparty%2Flxc.git fix the document according the current version Remove the comment about sharing /dev and fix the lxc-ps option format. Signed-off-by: Daniel Lezcano --- diff --git a/doc/lxc.sgml.in b/doc/lxc.sgml.in index 85988da3d..961a967fe 100644 --- a/doc/lxc.sgml.in +++ b/doc/lxc.sgml.in @@ -230,13 +230,11 @@ rootfs Running a system inside a container is paradoxically easier than running an application. Why ? Because you don't have to care - about the resources to be isolated, everything need to be isolated - except /dev which needs to be remounted in - the container rootfs, the other resources are specified as being - isolated but without configuration because the container will set - them up. eg. the ipv4 address will be setup by the system - container init scripts. Here is an example of the mount points - file: + about the resources to be isolated, everything need to be + isolated, the other resources are specified as being isolated but + without configuration because the container will set them + up. eg. the ipv4 address will be setup by the system container + init scripts. Here is an example of the mount points file: [root@lxc debian]$ cat fstab @@ -425,7 +423,7 @@ rootfs following commands give this information: lxc-ls - lxc-ps -n foo + lxc-ps --name foo lxc-info -n foo @@ -449,11 +447,12 @@ rootfs container. Like lxc-ls, lxc-ps is built on top of ps and accepts the same options, eg: - - lxc-ps -n foo --forest - + lxc-ps --name foo --forest + will display the processes hierarchy for the processes + belonging the 'foo' container. - will display the process hierarchy for the container 'foo'. + lxc-ps --lxc + will display all the containers and their processes.