From: Cedric Le Goater <clg@fr.ibm.com>

changed /var location
Signed-off-by: Cedric Le Goater <clg@fr.ibm.com>

From: Cedric Le Goater <clg@fr.ibm.com>

fixed readlink to add an ending '\0'
Signed-off-by: Cedric Le Goater <clg@fr.ibm.com>

From: Daniel Lezcano <dlezcano@fr.ibm.com>

Added the lxc-cgroup man page
Signed-off-by: Daniel Lezcano <dlezcano@fr.ibm.com>

From: Daniel Lezcano <dlezcano@fr.ibm.com>

Generate the man pages only if the docbook tool is available.
Signed-off-by: Daniel Lezcano <dlezcano@fr.ibm.com>

From: Daniel Lezcano <dlezcano@fr.ibm.com>

Added the different man pages for the lxc commands. The generation of the
man pages relies on the docbook tool.
Signed-off-by: Daniel Lezcano <dlezcano@fr.ibm.com>

From: Daniel Lezcano <dlezcano@fr.ibm.com>

This modification change the lxc-ps command and adds the lxc-ls command.

The lxc-ps command takes the container name argument and shows the processes
belonging to the specified container. The usual ps argument can be passed to
the lxc-ps to change the output.
Examples:
  lxc-ps -n foo --forest
  lxc-ps -n foo -o pid=

The lxc-ls command list the container name available on the system. This is
useful to retrieve information for each container.
Examples:
  for i in $(lxc-ls); do
	lxc-info -n $i
	lxc-ps -n $i --forest
  done
Signed-off-by: Daniel Lezcano <dlezcano@fr.ibm.com>

From: Daniel Lezcano <dlezcano@fr.ibm.com>

Return a lxc-error when for the lxc_configure and lxc_setup function.
Signed-off-by: Daniel Lezcano <dlezcano@fr.ibm.com>

From: Daniel Lezcano <dlezcano@fr.ibm.com>

Handle the lock error and show message to user.
Signed-off-by: Daniel Lezcano <dlezcano@fr.ibm.com>

From: Daniel Lezcano <dlezcano@fr.ibm.com>

Add the most known error to the different API to be followed up by the
caller, so we can later show a better message to the user when something
goes wrong. The error catching is coarse grain right now but will be improved,
step by step.
Signed-off-by: Daniel Lezcano <dlezcano@fr.ibm.com>

From: Daniel Lezcano <dlezcano@fr.ibm.com>

Added the error codes and the corresponding strings to the liblxc, so
the error raised to the user can be more understandable.
Signed-off-by: Daniel Lezcano <dlezcano@fr.ibm.com>

From: Daniel Lezcano <dlezcano@fr.ibm.com>

Do some cleanup in the lxc.h file, remove dead code and move definition to
the right place.
Signed-off-by: Daniel Lezcano <dlezcano@fr.ibm.com>

From: Daniel Lezcano <dlezcano@fr.ibm.com>

Remove the kill container processes code because it can be implemented with
a very few scripting lines
Signed-off-by: Daniel Lezcano <dlezcano@fr.ibm.com>

From: Daniel Lezcano <dlezcano@fr.ibm.com>

Setup the control group when executing the container.
Remove the dead code.
Signed-off-by: Daniel Lezcano <dlezcano@fr.ibm.com>

From: Daniel Lezcano <dlezcano@fr.ibm.com>

The future kernel version will automatically autodestroy the network devices
when the network namespace exits. This is not the case for the current version.
In order to handle the both cases, I added a configuration option to disable
the network destruction when the container exits:
	--disable-network-destroy
Signed-off-by: Daniel Lezcano <dlezcano@fr.ibm.com>

From: Daniel Lezcano <dlezcano@fr.ibm.com>

This modification change the configuration format. Instead of creating
a 'cgroup' directory with a file per controller, a single file is used
to store the different value for the control groups. That allows to assign
several values to the same controller like "devices.allow" and keep the same
assignation order as defined in the configuration.

In order to keep compatibility, when the old cgroup format is detected, it
is automatically converted to the new format.
Signed-off-by: Daniel Lezcano <dlezcano@fr.ibm.com>

From: Daniel Lezcano <dlezcano@fr.ibm.com>

When no command is specified is specified for lxc-start, the "/sbin/init"
is automatically used.
Signed-off-by: Daniel Lezcano <dlezcano@fr.ibm.com>

From: Daniel Lezcano <dlezcano@fr.ibm.com>

Previously, we dropped the CAP_SYS_BOOT capabilty. Unfortunatly if we are
non root user, we are not able to do that. So I had the CAP_SETPCAP to
lxc-execute and lxc-start command line to remove this capabilty.
Signed-off-by: Daniel Lezcano <dlezcano@fr.ibm.com>

From: Daniel Lezcano <dlezcano@fr.ibm.com>

The lxc_start function prototype has been changed.
Signed-off-by: Daniel Lezcano <dlezcano@fr.ibm.com>

From: Daniel Lezcano <dlezcano@fr.ibm.com>

The main difference between lxc_start and lxc_execute is the latter creates
an intermediate process to wait for all the childs. That allows to support
daemons or orphan process group for the pid namespace.

Having such difference makes the code to be duplicate between the two
functions. So instead of doing this, I create an intermediate <init> program
which is in charge to launch the specified command. This command is the
lxc-init program taking different options:
 --mount-procfs : mount the proc filesystem before exec'ing the command
 --mount-sysfs : mount the sys filesystem before exec'ing the command

A double dash indicates the end of the options of lxc-init and the beginning
of the command to be launched.

To summarize:
 * lxc_execute function is no more.
 * lxc-execute command uses the lxc_start function and launch the specified
command via lxc-init
Signed-off-by: Daniel Lezcano <dlezcano@fr.ibm.com>

From: Daniel Lezcano <dlezcano@fr.ibm.com>

Fix trivial typo
Signed-off-by: Daniel Lezcano <dlezcano@fr.ibm.com>

From: Daniel Lezcano <dlezcano@fr.ibm.com>

CONTRIBUTING file give the guidelines to submit patches to this project.
MAINTAINERS contains the maintainer name and mailing list to send the patches.
Signed-off-by: Daniel Lezcano <dlezcano@fr.ibm.com>

Remove the CAP_SYS_BOOT capability from the bouding set, so we can poweroff,
halt, reboot the container safely without shutting down the real host.
Signed-off-by: Daniel Lezcano <dlezcano@fr.ibm.com>

To allow user to properly configure the location of lxcpath (/var/lxc),
it should be build based on variable 'localstatedir' instead of 'prefix'.

By default, localstatedir=$prefix/var
localstatedir can be set by the user during configure:

./configure --localstatedir=/var
Signed-off-by: Daniel Lezcano <dlezcano@fr.ibm.com>

Exit instead of returning in child process.
Signed-off-by: Daniel Lezcano <dlezcano@fr.ibm.com>

to be shipped with the release

the installation prefix and by adding some extra path to search for the
'setcap' command.

relies on the file capabilities, when the lxc commands are installed, the
sys/net admin capabilities are given to these files. These capabilities are
not available for the application running inside the container.

path of the child will be wrong in case of error.

compiled the kernel. It relies on /proc/config.gz, if it is not compiled,
the command will simply fail.
If a feature is missing but not mandatory, "disabled" keyword will appear
in yellow, if it is mandatory, it will appear in "red", otherwise the key
word "enabled" will appear in green.

several readers can attend the events from one or several containers.
The syntax of the command has been enhanced to interpret regular expressions.
If you want to monitor foo, lxc-monitor -n foo is the right command. If you
want to monitor foo and bar, you should specify lxc-monitor -n "foo|bar",
if you want to monitor all containers with the name beginning with 'foo',
you have to specify lxc-monitor -n "foo.*". More complex regexp can be specified
in accordance with the POSIX definitions, man regex (7).