Quoting Vallevand, Mark K (mark.vallev...@unisys.com): > I'm not doing anything special with the container or the socket file. The > container is based on the Ubuntu template and I'm running a single program in > the container. The program will create its socket file according to its > command line. A program in the host looks for the socket file in the > /var/lib/lxc/container/rootfs and uses it. It works.
Right, the question is only which paths we can most reliably count on to not be overmounted by the guest. I suppose we could say /lxc-monitor is a directory for such sockets, or just suggest using '/lxc-*' as the socket names ------------------------------------------------------------------------------ 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
