* Michael Biebl <bi...@debian.org> wrote: > CCing Jon, as maintainer of libcgroup he might be interested in this > discussion. > > Am 07.09.2010 23:12, schrieb Bastian Blank: > > On Tue, Sep 07, 2010 at 10:54:04PM +0200, Michael Biebl wrote: > >> On 07.09.2010 22:41, Bastian Blank wrote: > >>> And what does this help? There are n cgroup filesystem hierarchies. > >> Are you referring to cgroup fs like cpuset? They would be mounted below > >> /sys/fs/cgroup. > > > > sysfs does not support mkdir. How will you mount _n_ different > > hierarchies? > > In the thread I quoted, G-K H mentions that /sys/fs/cgroup would be a tmpfs.
I agree with not creating another top-level directory. I configured libcgroup to mount cgroupfs under /mnt/cgroup as an initial solution, but mounting in /sys/fs seems much more consistent with current conventions. > >>> As it is private to systemd anyway, the correct locations is somewhere > >>> below /var/lib/ > >> As systemd requires the cgroupfs during early boot, /var/lib is not an > >> option. > > > > There are other locations. /sys is system wide and not daemon specific. > > > > I remember discussions, where to mount the cgroupfs [1], some while ago, > and /sys was among the recommendations. More importantly though, it was > said that we should see what the kernel folks do. This discussion took place on the libcgroup mailing list as well [1], posting here for reference. Many suggested somewhere under /sys, but I don't believe a consensus was reached. [1]: http://sourceforge.net/mailarchive/message.php?msg_id=20091104063005.GC3560%40balbir.in.ibm.com Cheers -- Jon -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100914135146.ga1...@starquasia
