Re: [lxc-devel] Rethinking lxc-info a bit

2013-11-13 Thread Dwight Engen
On Wed, 13 Nov 2013 14:41:55 -0500 Stéphane Graber wrote: > Hello, > > We recently got reports of the recent changes to lxc-info breaking > existing scripts. > > While discusing those issues, I noticed a few points that I think are > worth discussing and addressing, I'm going to postpone alpha3

[lxc-devel] [PATCH] gather all locking related code into src/lxc/lxclock.c

2013-11-13 Thread S . Çağlar Onur
Signed-off-by: S.Çağlar Onur --- src/lxc/lxclock.c | 74 +-- src/lxc/lxclock.h | 3 +++ src/lxc/utils.c | 57 +- 3 files changed, 65 insertions(+), 69 deletions(-) diff --git a/src/lxc/lxclock.c b/src/

Re: [lxc-devel] Rethinking lxc-info a bit

2013-11-13 Thread Serge Hallyn
Quoting Stéphane Graber (stgra...@ubuntu.com): > Hello, > > We recently got reports of the recent changes to lxc-info breaking > existing scripts. In my own case, I have a host with several containers where a backup script uses 'lxc-info -n $container -p | awk ...' to get the init pid, then rsync

[lxc-devel] Rethinking lxc-info a bit

2013-11-13 Thread Stéphane Graber
Hello, We recently got reports of the recent changes to lxc-info breaking existing scripts. While discusing those issues, I noticed a few points that I think are worth discussing and addressing, I'm going to postpone alpha3 until that's done as the current state of things would break quite a bunc

[lxc-devel] [lxc/lxc] a9a0ed: introduce lxcapi_add_device_node and lxcapi_remove...

2013-11-13 Thread GitHub
Branch: refs/heads/master Home: https://github.com/lxc/lxc Commit: a9a0ed90dd1cdadd412576a45af16419efc0e939 https://github.com/lxc/lxc/commit/a9a0ed90dd1cdadd412576a45af16419efc0e939 Author: S.Çağlar Onur Date: 2013-11-13 (Wed, 13 Nov 2013) Changed paths: M src/lxc/lxcco

Re: [lxc-devel] [PATCH] introduce lxcapi_add_device_node and lxcapi_remove_device_node to API (v3)

2013-11-13 Thread Stéphane Graber
On Wed, Nov 13, 2013 at 12:39:00AM -0500, S.Çağlar Onur wrote: > Adding block/char devices to running container is a common operation so > provide a common implementation for users to consume. > > changes since v2; > * lets the user set an alternate path inside the container as Stéphane > suggest

[lxc-devel] [lxc/lxc]

2013-11-13 Thread GitHub
Branch: refs/heads/master Home: https://github.com/lxc/lxc -- DreamFactory - Open Source REST & JSON Services for HTML5 & Native Apps OAuth, Users, Roles, SQL, NoSQL, BLOB Storage and External API Access Free app hos

[lxc-devel] [lxc/lxc] ff4bac: introduce lxcapi_add_device_node and lxcapi_remove...

2013-11-13 Thread GitHub
Branch: refs/heads/master Home: https://github.com/lxc/lxc Commit: ff4bacf71a3078cb2b926bfb248266236da9b1eb https://github.com/lxc/lxc/commit/ff4bacf71a3078cb2b926bfb248266236da9b1eb Author: S.Çağlar Onur Date: 2013-11-13 (Wed, 13 Nov 2013) Changed paths: M src/lxc/lxcco

Re: [lxc-devel] [PATCH] introduce lxcapi_add_device_node and lxcapi_remove_device_node to API

2013-11-13 Thread Serge Hallyn
Quoting S.Çağlar Onur (cag...@10ur.org): > Adding block/char devices to running container is a common operation so > provide a common > implementation for users to consume. > > Signed-off-by: S.Çağlar Onur Acked-by: Serge E. Hallyn > --- > src/lxc/lxccontainer.c | 100 >

[lxc-devel] Network interface - netns migration bug

2013-11-13 Thread Bogdan Purcareata
Hello, I've encountered this bug with lxc-0.9.0, using the lxc-phys scenario - assigning a physical interface to a container. In my understanding, this is what happens when a container starts (well, the relevant parts): - the configuration file is parsed into a config structure - the kernel in