On Wed, 2011-12-07 at 19:53 +0100, Guido Jäkel wrote: > Yes, i found that. But with this i only might be able to start n containers > with *one* invocation of the script - that's not what i want to reach in > general. > > I'm sorry, but i re-read my script and found, that i'm using lxc-wait to > watch the container start. But of course, it's the same with this. > > In the moment, the only workaround seems to use a polling loop with an > auto-interrupted invocation like > > timeout 1s lxc-wait -n $CONTAINER -s $STATE > > > I'll have a look on the sources to understand the current mechanism and it's > limitations. Thank you for your explanations so far. >
As of today, lxc-monitor acts as a server: it binds to a fixed unix socket address in the abstract namespace. All containers send events to this unique address. I see two issues with this design: - only one lxc-monitor at a time - lxc-monitor can be started in a container and receive the events about all the other containers (security?) Daniel, do you have plans to change this ? -- Gregory Kurz gk...@fr.ibm.com Software Engineer @ IBM/Meiosys http://www.ibm.com Tel +33 (0)534 638 479 Fax +33 (0)561 400 420 "Anarchy is about taking complete responsibility for yourself." Alan Moore. ------------------------------------------------------------------------------ Cloud Services Checklist: Pricing and Packaging Optimization This white paper is intended to serve as a reference, checklist and point of discussion for anyone considering optimizing the pricing and packaging model of a cloud services business. Read Now! http://www.accelacomm.com/jaw/sfnl/114/51491232/ _______________________________________________ Lxc-devel mailing list Lxc-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/lxc-devel
