On Wed, 2011-06-15 at 21:03 +0200, Oleg Nesterov wrote: > Forgot to ask, > > On 06/15, Greg Kurz wrote: > > > > The need arises in the LXC community when one wants to send a signal from > > the host (aka. init_pid_ns context) to a container process for which one > > only knows the pid inside the container. > > I am just curious, why do you need this? > Because some LXC users run partially isolated containers (AKA. application containers started with the lxc-execute command). Some of the user code runs outside the container and some inside. Since lxc-execute uses CLONE_NEWPID, it's difficult for the external code to relate a pid generated inside the container with a task. There are regular requests on lxc-users@ about this. -- Gregory Kurz gkurz@xxxxxxxxxx Software Engineer @ IBM/Meiosys http://www.ibm.com Tel +33 (0)534 638 479 Fax +33 (0)561 400 420 "Anarchy is about taking complete responsibility for yourself." Alan Moore. _______________________________________________ Containers mailing list Containers@xxxxxxxxxxxxxxxxxxxxxxxxxx https://lists.linux-foundation.org/mailman/listinfo/containers
