On 05/31/2012 10:17 AM, David Rientjes wrote:
> Hmm....maybe need to mount cgroup in the container (again) and get an access
> to cgroup
> hierarchy and find the cgroup it belongs to......if it's allowed.
An application should always know the cgroup that its attached to and be
able to read its state using the command that I gave earlier.
I disagree. For simple applications, yes. For full containers, the
cgroup in which it lives in is considered part of the external world.
It should not have any kind of access to it.
Also, tools need to work transparently.
That's the same case with /proc/stat, used for top. We can't expect
people to recode top to work on containerized environments.
--
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
