> I think there is about 80% overlap between the two projects but >enough differences to be interesting. I'll take a closer look at your >script looking for ideas I may have missed, and I invite you to do the same.
@Derek: well-spoken. @Daniel & Serge: Is there already something like a Wiki to collect such "contribute" work? I think, there are much more people around here which have developed such tools around LXC: Focused on their own requirements and conditions and therefore not fitted to publish to the community. But usefull to study for others to take an idea of it for own purposes. I also had to made my own lxc wrapper script to support my operation environment: To manage the arrangement and control of LXC containers running anywhere on a farm of identical LXC hosts. And as like as Ulli, I have written a lxc-free -- a substitute for free reflecting the memory values from the cgroup. Greetings Guido ------------------------------------------------------------------------------ All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2dcopy1 _______________________________________________ Lxc-users mailing list Lxc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/lxc-users
