On Mon, 07 May 2012 20:49:32 +0200, Sébastien Kalt wrote: > I've launched my kernel with cgroup_disable=memory : > > [ 0.000000] Command line: BOOT_IMAGE=/boot/vmlinuz-3.2.0-2-amd64 > root=UUID=d30adeed-998c-4f8b-b25c-185113da1cda ro cgroup_disable=memory > > Later in dmesg I have thoses lines : > > [ 0.010561] Initializing cgroup subsys cpuacct > [ 0.010657] Initializing cgroup subsys memory > [ 0.010762] Initializing cgroup subsys devices > [ 0.010855] Initializing cgroup subsys freezer > [ 0.010953] Initializing cgroup subsys net_cls > [ 0.011045] Initializing cgroup subsys blkio > [ 0.011156] Initializing cgroup subsys perf_event
I also get those lines with no extra parameter added. > Is cgroup memory really disabled ? I can't tell, it doesn't seem to be so (I would have expected a message saying it has been disabled) though it should, or at least that's what the docs say :-? > Anyway, I still have the same messages : > > May 7 20:06:48 crapaud64 console-kit-daemon[2468]: WARNING: Failed to add > monitor on '/dev/pts/2': No space left on device > May 7 20:07:04 crapaud64 console-kit-daemon[2468]: WARNING: Failed to add > monitor on '/dev/tty1': No space left on device We are still at the same place. It can be because: 1/ Cgroup is still enabled for memory handling. 2/ The printed mesages have no relation with this cgroup thingy :-) Are the above errors coming up when you are locally logged or when running from a remote system or when some specific configuration is in place (e.g., it happens when running an X session or launching a GUI application but does not when no X server is in place)? Greetings, -- Camaleón -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/jobcr2$vio$6...@dough.gmane.org
