On Wed, 13 Nov 2013 14:41:55 -0500 Stéphane Graber <stgra...@ubuntu.com> wrote:
> So my suggestion for lxc-info in LXC 1.0 are: > - Only support one container and make -n mandatory, fail with an error > if the container can't be found. I like the idea of lxc-info operating on a single container and have other tools to do multiple. vserver has a vserver-stat that will show the status of running vserver containers. I dunno if it would be an idea to introduce an lxc-stat tool and maybe move some of the 'fancy' features from lxc-ls to there too while at it. Example output from vserver-stat: build:~# vserver-stat CTX PROC VSZ RSS userTIME sysTIME UPTIME NAME 10005 2 23.2M 520K 0m00s23 0m00s26 43d00h06 nc-nptl 10007 1 19.6M 148K 0m00s27 0m00s18 43d00h06 build-1-10 10010 3 30.8M 1.3M 0m52s14 1m28s00 43d00h06 distfiles ... In situations where things go slow you want find out what container is using memory and cpu (and you often want do it quick). -nc
signature.asc
Description: PGP signature
------------------------------------------------------------------------------ DreamFactory - Open Source REST & JSON Services for HTML5 & Native Apps OAuth, Users, Roles, SQL, NoSQL, BLOB Storage and External API Access Free app hosting. Or install the open source package on any LAMP server. Sign up and see examples for AngularJS, jQuery, Sencha Touch and Native! http://pubads.g.doubleclick.net/gampad/clk?id=63469471&iu=/4140/ostg.clktrk
_______________________________________________ Lxc-devel mailing list Lxc-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/lxc-devel
