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

From: Grzegorz Nosek <grzegorz.nosek_at_gmail.com>
Date: Wed 21 Mar 2012 - 18:22:20 GMT
Message-ID: <4F6A1C5C.3070009@gmail.com>

W dniu 21.03.2012 16:47, Grzegorz Nosek pisze:
> 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).

Attached v2, this one is actually working *too* well -- the process tree
is shown *twice* on some occasions ;) Also, upstart works like a charm
(start/stop etc.)

This is another bug I won't fix today -- gotta go:

debian:/proc/sys/vserver# grep Tgid /proc/1/status
Tgid: 1
debian:/proc/sys/vserver# chcontext --xid 1 -- grep Tgid /proc/1/status
Tgid: 1
debian:/proc/sys/vserver# chcontext --xid 948 -- grep Tgid /proc/1/status
Tgid: 1
debian:/proc/sys/vserver# chcontext --xid 1 -- grep Tgid /proc/1/status
Tgid: 2219

Basically in xid==1 /proc/1 contains info about the last visited fakeinit.

Best regards,
  Grzegorz Nosek

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