This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "lxc".
The branch, master has been updated
via fd4f5a5688e511554ddd1f3fdbf1f05264b5b483 (commit)
via ef342abb22c1354b3523ce3c46e613e13ab79399 (commit)
via 36b862992a8e685534774a59793fb5c5bad46fae (commit)
via b234e44fdfb03ebb29f9bcb121d83e25b5a49800 (commit)
via 7c282e3cf4f46ee2e95589367904732f06c86af6 (commit)
via 4839ec2994ddf104fd135cdca9a48bebcd6e55f4 (commit)
via 59760f5d0f441c4d5ce165498abadcbd7409e9bb (commit)
from 968fbd36057db3132c68a63700e42929e5df5e2d (commit)
Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.
- Log -----------------------------------------------------------------
commit fd4f5a5688e511554ddd1f3fdbf1f05264b5b483
Author: Daniel Lezcano <daniel.lezc...@free.fr>
Date: Fri Dec 17 11:43:37 2010 +0100
use clone_children cgroup's flag
If the ns_cgroup does not exist, we use the clone_children feature.
Everytime a cgroup is created, we set this compatibility flag and we create
the cgroup manually and add the child task to the cgroup.
Signed-off-by: Daniel Lezcano <dlezc...@fr.ibm.com>
commit ef342abb22c1354b3523ce3c46e613e13ab79399
Author: Daniel Lezcano <daniel.lezc...@free.fr>
Date: Fri Dec 17 11:43:37 2010 +0100
Move common code to lxc_cgroup_create
For both the ns_cgroup and the usual cgroup creation, we have to
check if a previous does not exist and remove it if it is empty.
Signed-off-by: Daniel Lezcano <dlezc...@fr.ibm.com>
commit 36b862992a8e685534774a59793fb5c5bad46fae
Author: Daniel Lezcano <daniel.lezc...@free.fr>
Date: Fri Dec 17 11:43:37 2010 +0100
encapsulate the ns_cgroup
Create a single API to create a cgroup which will switch to the old
ns_cgroup automatically.
Signed-off-by: Daniel Lezcano <dlezc...@fr.ibm.com>
commit b234e44fdfb03ebb29f9bcb121d83e25b5a49800
Author: Daniel Lezcano <daniel.lezc...@free.fr>
Date: Fri Dec 17 11:43:37 2010 +0100
Change nscgroup interface
Prepare the nscgroup to be converted to the clone_children changes.
Signed-off-by: Daniel Lezcano <dlezc...@fr.ibm.com>
commit 7c282e3cf4f46ee2e95589367904732f06c86af6
Author: Daniel Lezcano <daniel.lezc...@free.fr>
Date: Fri Dec 17 11:43:37 2010 +0100
Remove unused nscgroup field
This field is unused.
Signed-off-by: Daniel Lezcano <dlezc...@fr.ibm.com>
commit 4839ec2994ddf104fd135cdca9a48bebcd6e55f4
Author: Daniel Lezcano <daniel.lezc...@free.fr>
Date: Fri Dec 17 11:43:36 2010 +0100
remove duplicate cgroup header
Signed-off-by: Daniel Lezcano <dlezc...@fr.ibm.com>
commit 59760f5d0f441c4d5ce165498abadcbd7409e9bb
Author: Michael Tokarev <m...@tls.msk.ru>
Date: Fri Dec 17 11:43:36 2010 +0100
Make mount paths relative to rootfs
Why not chdir into the root of container right when
the root filesystem is (bind-)mounted, and let all
mount entries to be relative to the container root?
Even more, to warn if lxc.mount[.entry] contains
absolute path for the destination directory (or a
variation of this, absolute and does not start with
container root mount point)?
This way, all mounts will look much more sane, and
it will be much easier to move/clone containers -
by changing only lxc.rootfs.
I do it this way locally since the beginning, by
chdir'ing to the proper directory (rootfs) before
running lxc-start (in a startup script), but this
is now broken in 0.7.3 which bind-mounts rootfs
somewhere in /usr/lib/lxc.
Signed-off-by: Michael Tokarev<m...@tls.msk.ru>
Signed-off-by: Daniel Lezcano <dlezc...@fr.ibm.com>
-----------------------------------------------------------------------
Summary of changes:
src/lxc/cgroup.c | 147 +++++++++++++++++++++++++++++++++++++------------
src/lxc/cgroup.h | 4 +-
src/lxc/conf.c | 45 ++++++++++++---
src/lxc/lxc_unshare.c | 2 +-
src/lxc/start.c | 5 +-
src/lxc/start.h | 1 -
6 files changed, 154 insertions(+), 50 deletions(-)
hooks/post-receive
--
lxc
------------------------------------------------------------------------------
Lotusphere 2011
Register now for Lotusphere 2011 and learn how
to connect the dots, take your collaborative environment
to the next level, and enter the era of Social Business.
http://p.sf.net/sfu/lotusphere-d2d
_______________________________________________
Lxc-devel mailing list
Lxc-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/lxc-devel
