[lxc-devel] [PATCH] Use container specific domain socket name

S.Çağlar Onur caglar at 10ur.org
Tue Apr 9 22:25:40 UTC 2013


Hi Serge,

On Tue, Apr 9, 2013 at 4:47 PM, Serge Hallyn <serge.hallyn at 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 <caglar at 10ur.org>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxcontainers.org/pipermail/lxc-devel/attachments/20130409/62a4d2df/attachment.html>


More information about the lxc-devel mailing list