- 10 Jun, 2009 2 commits
-
-
Daniel Lezcano authored
As we have the correct informations with pkg-config we can write a script which will collect the informations and we get rid of the C program. Signed-off-by:Daniel Lezcano <dlezcano@fr.ibm.com>
-
Daniel Lezcano authored
Add the pkg-config information for lxc. Signed-off-by:
-
- 07 Jun, 2009 6 commits
-
-
Daniel Lezcano authored
Don't clean up the sgml which are generated by configure, otherwise at the next make, the documentation generation will complain about missing files. Signed-off-by: -
Daniel Lezcano authored
When we daemonize the container and we specify the log file, the container will use the log file to write the console output. Signed-off-by: -
Daniel Lezcano authored
If needed the container can be launched in background with a specific option -d. That will make mute the container, the logs can help to check what went wrong. Signed-off-by: -
Daniel Lezcano authored
Save the tty configuration before calling lxc_start and restore it right after it has been changed. Signed-off-by: -
Filippo Giunchedi authored
Hi, as per subject, this ignores binaries generated in test/ Signed-off-by: -
Filippo Giunchedi authored
Hi, I've been playing with lxc, though with --enable-test the test/ directory doesn't compile, the following patch ought to fix this. I've not tested tests throughly but seems straightforward enough. Update the API usage in test/ as to make tests compile Signed-off-by:
-
- 29 May, 2009 1 commit
-
-
Daniel Lezcano authored
Signed-off-by:
-
- 28 May, 2009 17 commits
-
-
Michel Normand authored
the common options of lxc commands are now described in one file "common_options.sgml.in" Signed-off-by:
Michel Normand <normand@fr.ibm.com> Signed-off-by:
-
Michel Normand authored
the common references to lxc man pages are now placed in one file "see_also.sgml.in" Note that the few man pages that refer to man pages that are not lxc ones have two "See Also" paragraph. Signed-off-by:
-
Michel Normand authored
remove an error message in lxc_wait.c that duplicate an already existing error message in state.c Signed-off-by:
-
Michel Normand authored
Without this patch the lxc_wait may wait forever if container is already in requested state. Note that this patch avoids also to be hang if container do not exist yet. Signed-off-by:
-
Michel Normand authored
the change introduced by commit 31c53c2e do not allow anymore to have more than one monitor. The purpose of this patch is to add an error message when such a condition is identified, eg: === lxc-monitor: bind : Address already in use === Signed-off-by:
-
Daniel Lezcano authored
When no name is specified in the configuration file for an interface, let the system to choose one nice name like "eth". Signed-off-by: -
Daniel Lezcano authored
The lxc-unshare cli has changed, fix the call to lxc-unshare in lxc-netstat. Signed-off-by: -
Daniel Lezcano authored
Save the configuration file in the statefile directory so it can be re-created at restart time. Signed-off-by: -
Daniel Lezcano authored
add a statefile directory parameter in order to save some lxc informations a checkpoint. Signed-off-by: -
Daniel Lezcano authored
When creating the container, copy the configuration file to the configuration tree. Signed-off-by: -
Daniel Lezcano authored
Fix the code to not fail when the specified configuration file is empty. Signed-off-by: -
Daniel Lezcano authored
It is not easy to follow the cgroup name associated with a container, so right after the container is created, I rename the cgroup which is the pid of the creator by the container name. Signed-off-by: -
Daniel Lezcano authored
As the checkpoint/restart is expected to be sequential, I pass the file descriptor to checkpoint and restart, so that will be up to the caller to open the file descriptor which can be a pipe, socket, file, etc ... Signed-off-by: -
Daniel Lezcano authored
Removed this unused code. Signed-off-by: -
Daniel Lezcano authored
The checkpoint / restart code is too experimental regarding the current implementation in the kernel. As there are several implementation and we don't know which one will be merged upstream, I remove the code and add a few parameters to checkpoint. The checkpoint/restart function will be plugins in order to choose the CR solutions. This approach will allow to switch from one implementation to another without breaking anything. Signed-off-by: -
Daniel Lezcano authored
Now we have specific function to copy the files, make use of it and remove the old code. Signed-off-by: -
Daniel Lezcano authored
Create a specific function to copy a file from a location to another location. Signed-off-by:
-
- 18 May, 2009 14 commits
-
-
Michel Normand authored
There is no more need of the LXC_ERROR defines and related lxc_strerror function. Signed-off-by:
-
Michel Normand authored
This is useless because error is already reported by the functions Signed-off-by:
-
Michel Normand authored
to have same exit code for all lxc commands Signed-off-by:
-
Michel Normand authored
to have same exit code for all lxc commands Signed-off-by:
-
Michel Normand authored
to have same exit code for all lxc commands Signed-off-by:
-
Michel Normand authored
to have same exit code for all lxc commands Note that the lxc-restart is not yet reporting the error of restarted application as done with lxc-start. Signed-off-by:
-
Michel Normand authored
to have same exit code for all lxc commands Signed-off-by:
-
Michel Normand authored
there was a missing init of local variable Signed-off-by:
-
Michel Normand authored
to have same exit code for all lxc commands Signed-off-by:
-
Michel Normand authored
to have same exit code for all lxc commands Signed-off-by:
-
Michel Normand authored
to have same exit code for all lxc commands Signed-off-by:
-
Michel Normand authored
The exit code of the application as reported by lxc-execute is: 0-126 exit code of the application itself 128+n signal n received by the application 255 lxc error Note that this is the same type of changes as done for lxc-start command line. Signed-off-by:
-
Michel Normand authored
pass to lxc-init the log options given to lxc-execute (in fact logfile logpriority and quiet) Signed-off-by:
-
Michel Normand authored
The exit code of the application as reported by lxc-start is: 0-126 exit code of the application itself 128+n signal n received by the application 255 lxc error Signed-off-by:
-
