Package: lxc
Version: 0.8.0~rc1-8
Severity: important

Dear Maintainer,

   * What led up to the situation?

Started lxc-setcap as root, got the following message:

Failed to set capabilities on file `/lxc/lxc-init' (No such file or directory)

lxc-init is located in /usr/lib/x86_64-linux-gnu/lxc/ on my system,  no wonder
it failes.

The lxc-setcap script has the following statements:

   lxc_setcaps()
   {
       setcap $LXC_ATTACH_CAPS=ep /usr/bin/lxc-attach
       setcap $LXC_CREATE_CAPS=ep /usr/bin/lxc-create
       setcap $LXC_EXECUTE_CAPS=ep /usr/bin/lxc-execute
       setcap $LXC_START_CAPS=ep /usr/bin/lxc-start
       setcap $LXC_RESTART_CAPS=ep /usr/bin/lxc-restart
       setcap $LXC_UNSHARE_CAPS=ep /usr/bin/lxc-unshare
       setcap $LXC_NETSTAT_CAPS=ep /usr/bin/lxc-netstat
       setcap $LXC_CHECKPOINT_CAPS=ep /usr/bin/lxc-checkpoint
       setcap $LXC_INIT_CAPS=ep ${libexecdir}/lxc/lxc-init

       test -e ${localstatedir}/lib/lxc || mkdir -p ${localstatedir}/lib/lxc
       chmod 0777 ${localstatedir}/lib/lxc
   }

and also:

   libdir=/usr/lib/x86_64-linux-gnu/lxc
   localstatedir=/var

As you can see, there is a problem with libexecdir and localstatedir....

Hope this is easy to fix.

Kind regards,
Rob van der Hoeven.



-- System Information:
Debian Release: wheezy/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 3.2.0-2-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages lxc depends on:
ii  debconf [debconf-2.0]  1.5.44
ii  libc6                  2.13-33
ii  libcap2                1:2.22-1
ii  multiarch-support      2.13-33

Versions of packages lxc recommends:
ii  debootstrap  1.0.42
ii  libcap2-bin  1:2.22-1

Versions of packages lxc suggests:
pn  lxctl  <none>

-- debconf information:
  lxc/shutdown: /usr/bin/lxc-halt
* lxc/directory: /var/lib/lxc
  lxc/title:
  lxc/auto: true


-- 
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]

Reply via email to