On 11/10/2011 03:43 AM, 张勇 wrote:
Hi~:
I meet a error when i make lxc-0.7.5 on ubuntu 10.04.
The error info is :
Maybe the docbook tools are not available on your system.
You can prevent the documentation to be generated by specifying the
--disable-doc option for the configure script.
Hi,
lxc.network.ipv4 = 129.69.19.100/27
That helped, thank you!
--
Arie
On Wed, Nov 9, 2011 at 19:17, Ulli Horlacher
frams...@rus.uni-stuttgart.dewrote:
On Wed 2011-11-09 (18:15), Arie Skliarouk wrote:
It's all in http://fex.rus.uni-stuttgart.de/lxc-ubuntu
Whoa, so complicated!
To stop a virtual server, my l-stop script sends SIGINT signal first to the
init process of the container, then waits for up to 60 seconds (while
counting number of processes left) and then kills whatever remains.
After changing the ubuntu 10.04 vserver according to the
My mistake, this was possible with ubuntu 8.10 based containers and is no
longer possible with 10.04 containers. Not related to the recent changes.
Still, how can I gratefully stop the ubuntu 10.04 containers from the host
machine?
--
Arie
On Thu, Nov 10, 2011 at 14:11, Arie Skliarouk
Hi,
I have doubt in executing raw.write tests using lxc-execute.
When I execute it without lxc-execute it works fine i.e it performs
raw.write testing.
command :: root@nishant:/home/nishant/Desktop/samba-4.0.0alpha15#
bin/smbtorture //localhost/ubuntu -Ubase%base_system raw.write
This command
Signed-off-by: Serge Hallyn serge.hal...@canonical.com
---
templates/lxc-ubuntu.in |4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/templates/lxc-ubuntu.in b/templates/lxc-ubuntu.in
index 2be8680..d116f4c 100644
--- a/templates/lxc-ubuntu.in
+++
Particularly for LTS releases, which many people will want to use in
their containers, it is not wise to not use release-security and
release-updates. Furthermore the fix allowing ssh to allow the container
to shut down is in lucid-updates only.
With this patch, after debootstrapping a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 11/10/2011 04:42 PM, Serge E. Hallyn wrote:
Particularly for LTS releases, which many people will want to use
in their containers, it is not wise to not use release-security
and release-updates. Furthermore the fix allowing ssh to allow the
