[Lxc-users] regarding lxc "states" available to lxc-monitor or lxc-wait usage

[Serge Hallyn]

Quoting Vallevand, Mark K (Mark.Vallevand at 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