[Bug 1642767] Re: starting any container with umask 007 breaks host system shutdown. lxc-stop just hangs.

2017-04-12 Thread Pierre-Louis Bonicoli
My previous comment is unclear, the two problems are: 1. 'lxc' directories below '/sys/fs/cgroup/' are created according to the umask setting 2. then mounting '/sys/fs/cgroup/systemd' in the container hangs (and attempts to reboot or shut down the host system fail, a hard reset is required). --

[Bug 1642767] Re: starting any container with umask 007 breaks host system shutdown. lxc-stop just hangs.

2017-04-11 Thread Pierre-Louis Bonicoli
I was able to reproduce this bug on Debian unstable (lxc=2.0.7-2, libpam-cgfs=2.0.6-1, systemd=232-22, linux-image-4.9.0-2-amd64=4.9.18-1 or even using 4.11.0-rc6-1, libpam-cgm not installed, cgmanager not installed) with Debian Jessie unprivileged container (created using download template [1]). S

[Bug 480444] Re: packet storm with linux NFSv4 client when calling ftruncate()

2011-03-30 Thread Pierre-Louis Bonicoli
After updating some packages, i can not reproduce: - server & client: nfs-common 1.2.3-1, linux-image-2.6.38-1 - server: nfs-kernel-server 1.2.3, libgssglue 0.1-4 - client: libgssglue 0.2-2 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ub

[Bug 480444] Re: packet storm with linux NFSv4 client when calling ftruncate()

2011-03-21 Thread Pierre-Louis Bonicoli
Using bzr + nfsv4 i reproduce systematically ("bzr status" command non-interruptible even with kill -9. Using "umount -f " once or twice terminates bzr command). I add log statements (logs added with 'mutter' are stored in ~/.bzr.log) in "show_tree_status" from status.py. It appears that thi