I am not a developer, but an IT manager. I noticed, from business
standpoint, that once you have a large number of containers, with
identical processes, LXC becomes unmanageable.
I am the consumer of this technology. I am the "customer".
Yours
Philip
On Tue, May 20, 2014 at 11:16 PM, Fajar A. Nu
On Wed, May 21, 2014 at 7:07 AM, CDR wrote:
> Dear Friends
> I have 20+ containers with the same programs running. All of them are
> cpu-intensive. But one of them is eating way more CPU than the
> average. With "top" I have no idea which container "owns" that
> program. Perhaps we need a new "lxc
Hello CDR, ..
If your containers are accessible over ssh, you can iterate through the
containers and run a top or top-like command in each of them. You might
need unique users though.
for C in $(lxc-ls)
do
ssh $C "top -n 1"
sleep 1
done
On the other hand, yes, it would be practical to see t
Dear Friends
I have 20+ containers with the same programs running. All of them are
cpu-intensive. But one of them is eating way more CPU than the
average. With "top" I have no idea which container "owns" that
program. Perhaps we need a new "lxc-top" that would identify the
process and the container
As far as i remember, my hand compilation experience shows, that it is
really necessary
to build against python3 - otherwise all those "--fancy" options don't work.
___
lxc-users mailing list
lxc-users@lists.linuxcontainers.org
http://lists.linuxcontainer
done, this is great and seems to be working fine, at least it's as expected.
I'll copy in some container now and check that everything is all right.
I understand now I wasn't probably enabling enough option during
./configure, but it seemed odd that even the very basic options like
--version would
On Tue, 20 May 2014 17:36:39 +0800
coolnodje wrote:
> Just to make sure, since I've already tried to install 1.0.3 from
> source and didn't get something consistent with the doc: do you get
> commands that actually behave like described in linuxcontainers.org?
> I mean `lxc-ls --fancy`, `--versio
Hi,
you're right on time, I was just beginning to compile lxc from the
master branch and looking at options.
Thanks for the package, it sounds great.
Just to make sure, since I've already tried to install 1.0.3 from source
and didn't get something consistent with the doc: do you get commands
that
On Fri, 16 May 2014 10:43:11 +0200
Wojciech Arabczyk wrote:
> It would be best, if you'd try to create a deb package from the source
> package in sid, and then install via dpkg. Sorry, but i don't have
> time to provide specific instructions. You'll have to dig it out
> yourself.
If needed, one
