On Thu, 13.06.13 20:47, Tejun Heo (tj@xxxxxxxxxx) wrote: > cgroup's rename(2) isn't a proper migration implementation - it can't > move the cgroup to a different parent in the hierarchy. All it can do > is swapping the name string for that cgroup. This isn't useful and > can mislead users to think that cgroup supports proper cgroup-level > migration. Disallow rename(2) if sane_behavior. Note that in the long run I'd really like to see functionality added to move a full cgroup subtree to a different point in the tree, so that we can migrate containers and such atomically from one partition to another, without the container having to be aware of this (which of course implies that we have a somewhat more useful cgroup namespacing solution in place). Lennart -- Lennart Poettering - Red Hat, Inc. -- To unsubscribe from this list: send the line "unsubscribe cgroups" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
