On Mon, Jun 9, 2014 at 12:01 PM, CDR wrote:
> This is a killer issue. I plan to put all my business into LXC and
> take the load to 80%.
> Maybe it is not ready yet. Any advice?
A google search of "lxc vps" shows http://joes-cloud.com/lxc.html
thinks its ready for vps hosting purposes.
Personally
On 06/09/2014 07:01 AM, CDR wrote:
This is a killer issue. I plan to put all my business into LXC and
take the load to 80%.
Maybe it is not ready yet. Any advice?
Please check the link, that I posted recently.
tamas
___
lxc-users mailing list
lxc-us
This is a killer issue. I plan to put all my business into LXC and
take the load to 80%.
Maybe it is not ready yet. Any advice?
On Sun, Jun 8, 2014 at 6:30 PM, Tamas Papp wrote:
>
> On 06/08/2014 05:47 PM, Tamas Papp wrote:
>>
>>
>> Can it be HW issue?
>
>
> I finally found, that it is already re
On 06/08/2014 05:47 PM, Tamas Papp wrote:
Can it be HW issue?
I finally found, that it is already reported:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1315736
tamas
___
lxc-users mailing list
lxc-users@lists.linuxcontainers.org
http://l
Thanks for the help Stéphane and Serge.
I've set it up so that the host device is a bridge br0, I then assigned
those IP addresses which were previously aliases on eth0 to the containers
(configured with same gateway as the host) and connected them to the br0
bridge.
The network works fine intern
On 06/03/2014 05:34 PM, Tamas Papp wrote:
On 06/03/2014 05:08 PM, Stéphane Graber wrote:
On Tue, Jun 03, 2014 at 04:56:03PM +0200, Tamas Papp wrote:
On 06/03/2014 04:50 PM, Stéphane Graber wrote:
lxc-stop will send SIGPWR (or the equivalent signal) to the container,
wait 30s then SIGKILL ini
