On Sat, Aug 09, 2014 at 12:28:18AM +, Serge Hallyn wrote:
> The container command socket is an abstract unix socket containing
> the lxcpath and container name. Those can be too long. In that case,
> use the hash of the lxcpath and lxcname. Continue to use the path and
> name if possible to
On Fri, 2014-08-08 at 21:15 -0400, S.Çağlar Onur wrote:
> Hey Serge,
>
> On Fri, Aug 8, 2014 at 8:28 PM, Serge Hallyn wrote:
> > The container command socket is an abstract unix socket containing
> > the lxcpath and container name. Those can be too long. In that case,
> > use the hash of the lx
Hey Serge,
On Fri, Aug 8, 2014 at 8:28 PM, Serge Hallyn wrote:
> The container command socket is an abstract unix socket containing
> the lxcpath and container name. Those can be too long. In that case,
> use the hash of the lxcpath and lxcname. Continue to use the path and
> name if possible
The container command socket is an abstract unix socket containing
the lxcpath and container name. Those can be too long. In that case,
use the hash of the lxcpath and lxcname. Continue to use the path and
name if possible to avoid any back compat issues.
Signed-off-by: Serge Hallyn
---
src/l
