Hello,
I am trying to collects statistics from LXC container externally. By
externally, I mean without executing anything inside the container,
but just grabbing all the informations from the outside.
Basically I am processing like that:
Browse /var/lib/lxc to find containers name.
For each cont
Hi,
lxc_cgroup_path_get currently cache the cgroup mount point plus the
container name at the same time, making every call of the function
returning the same value.
It mean that actually every call to lxc_cgroup_get with a different
container name will in fact use the same container name as used f
Hi,
Here's a patch with the purpose adding a way to browse containers trough liblxc.
I added the function lxc-browse, that simply call back a function with
the container name as parameter.
It help to abstract how to browse containers without needed to know
the underlaying structure of LXC.
In cas
Oops, forgot to CC the mailing list!
here's my answer:
On Fri, Apr 15, 2011 at 9:58 AM, Francois-Xavier Bourlet
wrote:
> Yes I confirm what Gregory said. The purpose is to run some user code
> for each container (based on the name of it) for who link to the LXC
> library.
>
Hello,
Any news about a possible integration of my patch?
On Tue, Apr 19, 2011 at 12:57 PM, Francois-Xavier Bourlet
wrote:
> Oops, forgot to CC the mailing list!
>
> here's my answer:
>
> On Fri, Apr 15, 2011 at 9:58 AM, Francois-Xavier Bourlet
> wrote:
>> Yes I c
. So yes
I need to browse every running containers, and I guess that even if
the container is not registered but running, I can still collect all
the statistics.
Let me know what do you think!
thanks a lots for your review
On Tue, May 3, 2011 at 3:16 PM, Daniel Lezcano wrote:
> On 04/13/20
ri, May 6, 2011 at 4:26 PM, Daniel Lezcano wrote:
> On 05/04/2011 08:18 PM, Francois-Xavier Bourlet wrote:
>>
>> Hi,
>>
>> Ok I take note about inline patches in email.
>>
>> - About your version of lxc_for_each, your version is a lots better.
>> My co
Ok, thank a lots for the help! I am quite busy at this time, but soon
I will provide a clean patch.
Thanks again.
On Mon, May 9, 2011 at 1:48 PM, Daniel Lezcano wrote:
> On 05/07/2011 01:53 AM, Francois-Xavier Bourlet wrote:
>>
>> ok thanks for all the information and example.
Hi,
To be able to have setns (the syscall) support in lxc, you need to
have the linux kernel headers (or source).
Then the lxc build configuration system try to auto-detect the syscall
number using the linux kernel headers/sources. For that you need to
set an environ variable to help the build sy
