1. 18 Aug, 2014 2 commits
    • monitor: fix sockname calculation for long lxcpaths · 073135ba
      Serge Hallyn authored
      A long enough lxcpath (and small PATH_MAX through crappy defines) can cause
      the creation of the string to be hashed to fail.  So just use alloca to
      get the size string we need.
      
      More importantly, while I can't explain it, if lxcpath is too long, setting
      sockname[sizeof(addr->sun_path)-2] to \0 simply doesn't seem to work.  So set
      sockname[sizeof(addr->sun_path)-3] to \0, which does work.
      
      With this, and with
      
      lxc.lxcpath = /opt/lxc0123456789/lxc0123456789/lxc0123456789/lxc0123456789/lxc0123456789/lxc0123456789/lxc0123456789/lxc0123456789/lxc0123456789/lxc0123456789
      
      in /etc/lxc/lxc.conf, I can run lxc-wait just fine.  Without it, it fails
      (as does lxc-start -d, which uses lxc_wait to verify the container started)
      Signed-off-by: 's avatarSerge Hallyn <serge.hallyn@ubuntu.com>
      Acked-by: 's avatarStéphane Graber <stgraber@ubuntu.com>
    • command socket: use hash if needed · e8589841
      Serge Hallyn authored
      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: 's avatarSerge Hallyn <serge.hallyn@ubuntu.com>
      Acked-by: 's avatarStéphane Graber <stgraber@ubuntu.com>
  2. 16 Aug, 2014 14 commits
  3. 15 Aug, 2014 1 commit
  4. 08 Aug, 2014 11 commits
  5. 06 Aug, 2014 1 commit
  6. 04 Aug, 2014 11 commits