On 04/12/2011 04:14 PM, Marco d'Itri wrote:
On Apr 12, Daniel Lezcano wrote:
At the first glance udev events are supported in the container. But for
the sake of optimization, I recommend to not use it as it will trigger
the events in all the containers.
This looks wrong... containers should n
On Apr 12, Daniel Lezcano wrote:
> At the first glance udev events are supported in the container. But for
> the sake of optimization, I recommend to not use it as it will trigger
> the events in all the containers.
This looks wrong... containers should not be able to trigger events
which aff
On 04/11/2011 02:47 AM, Marco d'Itri wrote:
On Apr 06, Daniel Lezcano wrote:
I would not rely on that because lxc may evolve to not use the cgroup if
not present.
If you use upstart, you can check the 'container=lxc' env variable in
the udev init script in order to know if you are in a contai
On Apr 06, Daniel Lezcano wrote:
> If you use upstart, you can check the 'container=lxc' env variable in
> the udev init script in order to know if you are in a container.
> Otherwise for sysvrc init, I don't know how to handle that.
Sad, the LXC user space always looked quite rough and amate
On Apr 06, Daniel Lezcano wrote:
> I would not rely on that because lxc may evolve to not use the cgroup if
> not present.
>
> If you use upstart, you can check the 'container=lxc' env variable in
> the udev init script in order to know if you are in a container.
> Otherwise for sysvrc init
On 04/05/2011 09:23 PM, Cyril Brulebois wrote:
Hi LXC folks,
from my bug report against udev, so that it doesn't try to start when
running in a non-root container:
Marco d'Itri (05/04/2011):
On Apr 05, Cyril Brulebois wrote:
from a quick glance, it looks like running udev in a linux
contai
6 matches
Mail list logo
