Hello, I understand that LXC uses sandboxing heavily. After taking a look at the source I don't think that LXC uses multithreading and that it tries to accomplish any multiprocessing needs by forking instead. However, the topic I am about to bring up may be relevant if LXC wishes to use multithreading in the future. After a fork, many things are messed up so it's only practical to use async-signal-safe functions after a fork from a threaded program. If you have ideas on what sort of functionality GLibc needs to change to make required functionality more async-signal-safe after a fork from a multithreaded program you are invited to give your thoughts on the GLibc mailing list in the thread at https://sourceware.org/ml/libc-help/2014-08/msg00039.html. I am not subscribed to lxc-devel so you may want to CC me.
Thank you, Steven Stewart-Gallus _______________________________________________ lxc-devel mailing list lxc-devel@lists.linuxcontainers.org http://lists.linuxcontainers.org/listinfo/lxc-devel
