On Mon, Nov 18, 2013 at 05:09:31PM +0100, Pavel Hrdina wrote:
> On 15.11.2013 17:20, Daniel P. Berrange wrote:
> >The glibc setxid is supposed to be async signal safe, but
> >libc developers confirm that it is not. This causes a problem
> >when libvirt_lxc starts the FUSE thread and then runs clone
On 15.11.2013 17:20, Daniel P. Berrange wrote:
The glibc setxid is supposed to be async signal safe, but
libc developers confirm that it is not. This causes a problem
when libvirt_lxc starts the FUSE thread and then runs clone()
to start the container. If the clone() was done before the
FUSE thre
On 11/16/2013 12:20 AM, Daniel P. Berrange wrote:
> The glibc setxid is supposed to be async signal safe, but
> libc developers confirm that it is not. This causes a problem
> when libvirt_lxc starts the FUSE thread and then runs clone()
> to start the container. If the clone() was done before the
On Fri, Nov 15, 2013 at 10:37:53AM -0700, Eric Blake wrote:
> On 11/15/2013 09:20 AM, Daniel P. Berrange wrote:
> > The glibc setxid is supposed to be async signal safe, but
> > libc developers confirm that it is not. This causes a problem
> > when libvirt_lxc starts the FUSE thread and then runs c
On 11/15/2013 09:20 AM, Daniel P. Berrange wrote:
> The glibc setxid is supposed to be async signal safe, but
> libc developers confirm that it is not. This causes a problem
> when libvirt_lxc starts the FUSE thread and then runs clone()
> to start the container. If the clone() was done before the
The glibc setxid is supposed to be async signal safe, but
libc developers confirm that it is not. This causes a problem
when libvirt_lxc starts the FUSE thread and then runs clone()
to start the container. If the clone() was done before the
FUSE thread has completely started up, then the container
