Daniel Lezcano wrote, On 2010. 08. 30. 11:26: > Hmm, too bad :) I was about to ask you some informations about the > processes of the containers.
Well, I was happy too early. > If that happens again, can you check/report the following : > > * the content of the tasks file in the cgroup directory ? Killing lxc-start make the container disappear only from lxc-ls's output. In the tasks file I saw three processes: udevd, init and one more, which I don't remember. I killed them all, but the cgroup still exists. > * the state of the processes of the containers (stopped or not) I don't know, what do you mean on stopped. Is there any available? > * and the state of the lxc-start process ( cat /proc/<pid>/stack ) Well, next time. > Was the lxc-stop blocked ? Nope. Now, I could stop it. I could remove the containers directory, then copy there a new install tarball. After that, lxc-destroy, than start, then stop and finally I'm happy again. But I'm afraid this won't help you to debug it:( Thanks, tamas ------------------------------------------------------------------------------ Sell apps to millions through the Intel(R) Atom(Tm) Developer Program Be part of this innovative community and reach millions of netbook users worldwide. Take advantage of special opportunities to increase revenue and speed time-to-market. Join now, and jumpstart your future. http://p.sf.net/sfu/intel-atom-d2d _______________________________________________ Lxc-users mailing list Lxc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/lxc-users
