On 05/09/2011 10:58 PM, Francois-Xavier Bourlet wrote:
> Ok, thank a lots for the help! I am quite busy at this time, but soon
> I will provide a clean patch.
Cool, I believe this function will help for my ncurse based prototype :)
-
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.
>>
>> I believe th
On 05/07/2011 01:53 AM, Francois-Xavier Bourlet wrote:
ok thanks for all the information and example.
I believe that rather than trying to iterate over every containers
running or not and trying to merge the result we could simply iterate
only on running container, or only stopped container (I s
ok thanks for all the information and example.
I believe that rather than trying to iterate over every containers
running or not and trying to merge the result we could simply iterate
only on running container, or only stopped container (I simplify). So
lxc_for_each could simply take a state in pa
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 code was totally stupid and non-performant. In fact I based my code
> on something else that was needed the sc
Hi,
Ok I take note about inline patches in email.
- About your version of lxc_for_each, your version is a lots better.
My code was totally stupid and non-performant. In fact I based my code
on something else that was needed the scandir, i simply copy/pasted by
laziness. About the full path, in fa
On 04/13/2011 07:49 PM, Francois-Xavier Bourlet wrote:
> 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 contai
On 05/02/2011 07:29 PM, Francois-Xavier Bourlet wrote:
> Hello,
>
> Any news about a possible integration of my patch?
Sorry François-Xavier for the delay. Let me review the patch this evening.
Thanks
-- Daniel
--
W
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 confirm what Gregory said. The p
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.
>
> I am actually worki
On 04/15/2011 06:43 PM, Greg Kurz wrote:
> On Fri, 2011-04-15 at 10:00 -0500, Rob Landley wrote:
>> On 04/13/2011 12:49 PM, Francois-Xavier Bourlet wrote:
>>> Hi,
>>>
>>> Here's a patch with the purpose adding a way to browse containers trough
>>> liblxc.
>>
>> What does "browse" mean in this cont
On Fri, 2011-04-15 at 10:00 -0500, Rob Landley wrote:
> On 04/13/2011 12:49 PM, Francois-Xavier Bourlet wrote:
> > Hi,
> >
> > Here's a patch with the purpose adding a way to browse containers trough
> > liblxc.
>
> What does "browse" mean in this context?
>
By reading the code, "browse" seems
On 04/13/2011 12:49 PM, Francois-Xavier Bourlet wrote:
> Hi,
>
> Here's a patch with the purpose adding a way to browse containers trough
> liblxc.
What does "browse" mean in this context?
> I added the function lxc-browse, that simply call back a function with
> the container name as parameter
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
14 matches
Mail list logo
