On 06/16, Greg Kurz wrote: > > 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. Well, this doesn't answer my question ;) Why do you need to send the signal into the sub-namespace, and how/why do you know the pid inside the container. OK, nevermind, I was just curious. Oleg. _______________________________________________ Containers mailing list Containers@xxxxxxxxxxxxxxxxxxxxxxxxxx https://lists.linux-foundation.org/mailman/listinfo/containers
