Hi,
Indeed, we were refering to the network bandwidth limitation. Sorry for the
confusion.
We have already done some tests with this limitation using tc and cgroups
and we have reached the conclusion that the classification is done
correctly, but the limitation of the bandwidth is not done at all
lxc watches /var/run/utmp in the container to monitor its runlevel, so that
it can stop or "reboot" the container when appropriate. This should not
happen though if the container shares /var/run/utmp with the system (which
should only be the case if the container does not run init).
Currently this
The two variables I added have misleading names. I will fix these,
clarify the commit message, and resend shortly.
David
On 02/28/2011 07:08 PM, Ward, David - 0663 - MITLL wrote:
lxc watches /var/run/utmp in the container to monitor its runlevel, so that
it can stop or "reboot" the container
In order to stop or restart a container that runs "init" as its top-level
process, lxc must watch for changes to the "utmp" file (which stores init's
current and previous runlevel) located in /var/run in the container. Because
lxc should only react to the container runlevel (if one exists) and not
