Excerpts from Matthew Cluver's message of Tue Aug 10 12:59:51 -0700 2010:
> I'm not sure if you've seen the message on github, I wanted to respond
> here to make sure that you'd seen it. I've tested and confirmed that
> the patch Kai submitted will work correctly moving forward.
Thanks Matt. I'm m
Rein,
I'm not sure if you've seen the message on github, I wanted to respond
here to make sure that you'd seen it. I've tested and confirmed that
the patch Kai submitted will work correctly moving forward.
Regards,
Matt
On Aug 9, 4:20 pm, Rein Henrichs wrote:
> Excerpts from Matthew Cluver's m
Excerpts from Matthew Cluver's message of Mon Aug 09 11:42:12 -0700 2010:
> Hi Rein,
>
> I have been using the code above in the openvz module as it is working
> for my needs (0.25.5-1) at the current moment. I have no problem using
> the proposed patch, my main goal is to simply get a working and
Hi Matt,
Thank you for sharing the libvirt project with me, it looks like that
is what we're going to want to work on migrating into at some point.
At this moment what I have for openvz is working but very crude at the
moment, as it is nearly a wrapper for the vzctl executable.
Matt
On Aug 6, 4
Hi Rein,
The patch that was presented by Kai I believe will work, I originally
missed where they continue to check after the original directory /proc/
vz check. Unfortunately, if this is the best that we can do using
native code, we might be stuck with it for now due to the limitations
of OpenVZ.
On Thursday 23 April 2009 04:50:10 Justin B Newman wrote:
> It appears that the client application opens a tcp socket for every
> one of those files when it runs, as it computes the checksum. When it
> hits 1024 sockets open, it is unable to open additional sockets. This
I had exactly the same p
