On 06/26/2011 05:52 PM, Michael H. Warfield wrote: > On Sun, 2011-06-26 at 17:27 +0200, Daniel Lezcano wrote: >> On 06/26/2011 05:06 PM, Serge E. Hallyn wrote: >>> Quoting Michael H. Warfield (m...@wittsend.com): >>>>> cd /sys/fs/cgroup >>>>> for d in `/bin/ls`; do >>>>> echo 1 > $d/cgroup.clone_children >>>>> done >>>> >>>> Doing this step alone broke lxc totally for me, with or without the >>>> patch below. This was on Fedora 15 testing with lxc 0.7.4.2 as well as >>> >>> Do you have the ns cgroup mounted? The above is only for without >>> ns cgroup. > >> Yes, the ns_cgroup and clone_children are mutually exclusive. > >> If you try to create a namespace with a ns cgroup mounted and the >> clone_children flag is set. The 'clone' will return EINVAL. > >> I noticed with the patch applied because there was a bug in it which was >> setting this flag even if the cgroup was ns. > >> It is possible, you ran lxc with the patch, the clone_children was set, >> and then you remove the patch and try to run lxc again. As the >> clone_children is still set, that will make impossible to clone a new >> namespace. > >> With the patch I sent previously on top of Serge's patch, that should be >> fixed. > > Ok... Got that an threw it into the mix. > > I'm still seeing the segfaults on lxc-info. Seems to fault even if I > specify the name of a non-existent machine as well.
Oh, seems I missed this info :s If you launch lxc-info -n foo, that segfaults ? On what architecture does it fault ? ------------------------------------------------------------------------------ All of the data generated in your IT infrastructure is seriously valuable. Why? It contains a definitive record of application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-d2d-c2 _______________________________________________ Lxc-users mailing list Lxc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/lxc-users
