| Re: Hidden process for init (PID 1)? [message #34229 is a reply to message #34228] |
Mon, 15 December 2008 11:55   |
signal11
Messages: 3
Registered: December 2008
|
Junior Member |
|
|
| maratrus wrote on Mon, 15 December 2008 06:39 |
Hello,
| Quote: |
I'm aware that OpenVZ already has a hidden process for every visible process in the container
|
No, OpenVZ doesn't have a hidden process for every visible in the container. The process that is shown inside container is the same process that is shown on the HN (you should be able to manipulate your VE from inside the HN). But as we consider container as a standalone system we should support container's own pid space, that's why the process with pid = pid_ve is shown as a pid_ve + 1024 on the HN.
But OpenVZ doesn't change processes' names so we must find on the HN init processes for every VE running on that moment.
|
That doesn't answer the question, though: is it normal that (exactly) one hidden process does not follow the 'offset by 1024' rule? (and nitpicking aside, within the container it appears as a second, 'hidden' process.. what it really is is another issue).
But as far as I understand, every process in the container is a process on the host, usually with a fixed offset in PID. This would work for every process except init, which always has PID 1, so the associated PID on the host cannot follow the 'offset by 1024' rule, because with several containers you need several processes corresponding to init in these containers. I just wanted to know whether this interpretation is (more or less) correct.
|
|
|
|
OpenVZ Forum
Members
Search
Help
Register
Login
Home
