All right you made me finally take a closer look at the monitor code (which I'd been avoiding). It's much simpler than I'd imagined. So here are the challenges:
1. lxc-monitor should be able to watch 'all containers' (at least under a given lxcpath). That is actually the strong reason to object to your patch. 2. we don't want to force any long-running daemon to run as the monitor. 3. we want to allow multiple containers to send state change info to multiple simulataneous lxc-monitor and lxc-wait listeners. Now I can think of some whacky solutions, but are there any simple ones I'm overlooking? -serge ------------------------------------------------------------------------------ Precog is a next-generation analytics platform capable of advanced analytics on semi-structured data. The platform includes APIs for building apps and a phenomenal toolset for data science. Developers can use our toolset for easy data analysis & visualization. Get a free account! http://www2.precog.com/precogplatform/slashdotnewsletter _______________________________________________ Lxc-devel mailing list Lxc-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/lxc-devel
