Hi Serge,
On Tue, Apr 9, 2013 at 4:47 PM, Serge Hallyn <serge.hal...@ubuntu.com>wrote:
> 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.
>
Ah, that makes sense.
> 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?
I'm not sure what is your whacky solution but if I'm not missing something
this sounds like multicast :) I'm sorry for my ignorance but did multicast
unix sockets patch set find its way into upstream kernel?
> -serge
>
Cheers,
--
S.Çağlar Onur <cag...@10ur.org>
------------------------------------------------------------------------------
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
