This bug was fixed in the package udev - 175-0ubuntu5
---
udev (175-0ubuntu5) precise; urgency=low
[ David Henningsson ]
* Remove jack-detection.patch: Now that PulseAudio uses the new jack
detection interface, we can remove this patch.
[ Stéphane Graber ]
*
My guess is that juju is setting umask somewhere? The mode passed to
mkdir(2) is 'd with the task's umask. The code in lxc definately
passes 0755 as the mode. We could patch lxc to do an explicit chmod
after the fact, but that seems like the wrong thing to do. The umask -
ideally - was set as
In my opinion, the fix here is for juju to set its umask to 0022 before
calling lxc-start
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/925122
Title:
container's udevadm trigger --add
(please feel free to re-mark confirmed for lxc if you disagree :)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/925122
Title:
container's udevadm trigger --add affects the host
To
wrapping lxc-start confirms umask is 0077 when lxc-start is called
through juju.
** Changed in: lxc (Ubuntu)
Status: Confirmed = Invalid
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
I applied the change to our packaging branch for udev but didn't upload
yet as the new upstart failed to build on armel, armhf and powerpc.
Uploading the change with the current upstart would most likely break if
not slow down the boot.
** Changed in: udev (Ubuntu)
Status: Confirmed = Fix
