On 02/24/2014 03:36 PM, Serge Hallyn wrote: > Quoting Tamas Papp ([email protected]): >> On 02/22/2014 06:25 AM, Serge Hallyn wrote: >>> Ok, thanks Tamas - this is a bug in how the cgproxy starts up >>> on an older kernel. >>> >>> As a workaround until I get it fixed, you can >>> >>> sudo stop cgproxy >>> sudo stop cgmanager >>> sudo rm -rf /sys/fs/cgroup/cgmanager* >>> >>> then in one terminal: >>> >>> sudo /sbin/cgmanager --debug >>> >>> and in another: >>> >>> sudo /sbin/cgproxy --debug >>> >> hi Serge, >> >> Precise: > Hi, > > these look fine to me. Are you saying this worked, or did > not work?
Did not work. >> There is no cgproxy.. > ? You mean /sbin/cgproxy does not exist? I don't know, probably I was too tired. BTW, I meant there was no cgproxy _package_, but I can see, there is no cgproxy package anywhere...don't know, why I thought...sorry. Anyway, the point is, that it doesn't work on precise and saucy. Does it work for you? >> ps.: /bin/ls sometime list / sometime /root. I could not figure out the >> logic. Is there any, or may it be another bug? > I don't understand. You typed /bin/ls in the container and sometimes > see / and sometimes root? How are you logging in? lxc-attach? I didn't login just run '/bin/ls' lxc-attach -n container /bin/ls But forget it, I'll come back, if I can reproduce it or I have more details. tamas _______________________________________________ lxc-users mailing list [email protected] http://lists.linuxcontainers.org/listinfo/lxc-users
