Re: [vserver] Getting a real pid 1 init in a container

From: Grzegorz Nosek <>
Date: Wed 21 Mar 2012 - 15:47:17 GMT
Message-ID: <>

W dniu 21.03.2012 14:56, Grzegorz Nosek pisze:
> I looked through the patch and all this reaper stuff ends up modifying
> vx_info->reaper, which AFAICS is not used anywhere. I downloaded the 3.3
> patch[1] and it looks the same. The relevant function seems to be
> find_new_reaper() from kernel/exit.c as of 2.6.27.y:

A basically working patch attached. One weird side effect is that the
container init and its children are not visible in `vps auxf` (they
remain visible in `vps aux` though).

It happens because now the container init has itself as the ppid and is
totally disconnected from the normal process hierarchy. Not quite sure
how the ppid got set that way, will have another look.

Patch is based on my 2.6.27.y, but looking at 3.3, the function is
unchanged, except for a lockdep (or something) annotation.

Best regards,
  Grzegorz Nosek

Received on Wed Mar 21 15:47:43 2012
[Next/Previous Months] [Main vserver Project Homepage] [Howto Subscribe/Unsubscribe] [Paul Sladen's vserver stuff]
Generated on Wed 21 Mar 2012 - 15:47:43 GMT by hypermail 2.1.8