man update lxc-execute and lxc-start (V2)

Signed-off-by: Michel Normand <normand@fr.ibm.com>
Signed-off-by: Daniel Lezcano <dlezcano@fr.ibm.com>
This commit is contained in:
Michel Normand 2010-04-29 10:03:59 +02:00 committed by Daniel Lezcano
parent a941cc0bf6
commit 94b81f611f
2 changed files with 46 additions and 32 deletions

View File

@ -60,20 +60,32 @@ Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA
<title>Description</title> <title>Description</title>
<para> <para>
<command>lxc-execute</command> runs <command>lxc-execute</command> runs the specified
the <replaceable>command</replaceable> inside the container <replaceable>command</replaceable> inside the container
specified by <replaceable>name</replaceable>. This command specified by <replaceable>name</replaceable>.
should be used to launch an application, eg. sshd or bash. </para>
<para>
It will setup the container
according to the configuration previously defined with the
lxc-create command or with the configuration file parameter.
If no configuration is
defined, the default isolation is used.
</para> </para>
<para> <para>
This command is mainly used when you want to quickly launch an This command is mainly used when you want to quickly launch an
application in an isolated environment. It will create an application in an isolated environment.
intermediate process allowing you application to daemonize in
the pid namespace and will mount the proc filesystem to complete
the pid isolation.
</para> </para>
<para>
<command>lxc-execute</command> command will run the
specified command into the container via an intermediate
process, <command>lxc-init</command>.
This lxc-init after launching the specified command,
will wait for its end and all other reparented processes.
(that allows to support daemons in the container).
In other words, in the
container, <command>lxc-init</command> has the pid 1 and the
first process of the application has the pid 2.
</para>
</refsect1> </refsect1>
<refsect1> <refsect1>
@ -82,18 +94,23 @@ Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA
<varlistentry> <varlistentry>
<term> <term>
<option>-f <replaceable>config_file</replaceable></option> <option>-f, --rcfile <replaceable>config_file</replaceable></option>
</term> </term>
<listitem> <listitem>
<para> <para>
Specify the configuration file to configure the virtualization Specify the configuration file to configure the virtualization
and isolation functionalities for the container. and isolation functionalities for the container.
</para> </para>
<para>
This configuration file if present will be used even if there is
already a configuration file present in the previously created
container (via lxc-create).
</para>
</listitem> </listitem>
</varlistentry> </varlistentry>
<varlistentry> <varlistentry>
<term> <term>
<option>-s <replaceable>KEY=VAL</replaceable></option> <option>-s, --define <replaceable>KEY=VAL</replaceable></option>
</term> </term>
<listitem> <listitem>
<para> <para>

View File

@ -57,20 +57,27 @@ Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA
<title>Description</title> <title>Description</title>
<para> <para>
<command>lxc-start</command> runs the specified command inside <command>lxc-start</command> runs the specified
the container specified by name. It will setup the container <replaceable>command</replaceable> inside the container
according the configuration previously defined with the specified by <replaceable>name</replaceable>.
lxc-create command or with the configuration file parameter and </para>
execute the command inside the container. If no configuration is <para>
defined, the default isolation is used. The orphan process group It will setup the container
according to the configuration previously defined with the
lxc-create command or with the configuration file parameter.
If no configuration is
defined, the default isolation is used.
</para>
<para>
The orphan process group
and daemon are not supported by this command, use and daemon are not supported by this command, use
the <command>lxc-execute</command> command instead. the <command>lxc-execute</command> command instead.
</para>
<para>
If no command is specified, <command>lxc-start</command> will If no command is specified, <command>lxc-start</command> will
use the default use the default
<command>"/sbin/init"</command> command to run a system <command>"/sbin/init"</command> command to run a system
container. container.
</para> </para>
</refsect1> </refsect1>
@ -96,7 +103,7 @@ Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA
<varlistentry> <varlistentry>
<term> <term>
<option>-f <replaceable>config_file</replaceable></option> <option>-f, --rcfile <replaceable>config_file</replaceable></option>
</term> </term>
<listitem> <listitem>
<para> <para>
@ -108,7 +115,7 @@ Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA
<varlistentry> <varlistentry>
<term> <term>
<option>-s <replaceable>KEY=VAL</replaceable></option> <option>-s, --define <replaceable>KEY=VAL</replaceable></option>
</term> </term>
<listitem> <listitem>
<para> <para>
@ -141,16 +148,6 @@ Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA
</listitem> </listitem>
</varlistentry> </varlistentry>
<varlistentry>
<term>The container was not found</term>
<listitem>
<para>
The specified container was not created before with
the <command>lxc-create</command>
</para>
</listitem>
</varlistentry>
</variablelist> </variablelist>
</refsect1> </refsect1>