Quoting Vallevand, Mark K (mark.vallev...@unisys.com): > I don't think signals to the container init process is the answer. You can > run a single program in a container. When that program reaches a certain > state, it could report that it is operational. I don't know what the correct > way to do that report using a new lxc feature. > > Currently, my program creates a file that indicates it is operational. My > container start-up code looks for that file before it assumes that the > container is ready.
Right, that's what I'd probably do. We can't really pass the info over a socket since the container is likely in a separate netns. Signals require that (a) the container's init be in on it, and (b) that container init get the signals and (c) have a way to pass them on. Solving this in a generic way doesn't seem easy. ------------------------------------------------------------------------------ Learn Graph Databases - Download FREE O'Reilly Book "Graph Databases" is the definitive new guide to graph databases and their applications. This 200-page book is written by three acclaimed leaders in the field. The early access version is available now. Download your free book today! http://p.sf.net/sfu/neotech_d2d_may _______________________________________________ Lxc-users mailing list Lxc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/lxc-users
