the init-process of a VServer (Gentoo-VPS is started via init) naturally gets
a PID > 1 in the host-context, but this PID ist remapped to 1 in the
VPS-context. Is this a simple mapping done by the vserver-patches? I could
not spot this in the patch-set ... I think this is part of the virtualization
of the procfs similar to /proc/uptime. Can someone give me a hint?
Additionally, what happened in the case of a Debian-VPS, which is started
via /etc/init.d/rc 3 ? I can't read all the entries in /proc/1:
vs03:~# ls -l /proc/1
ls: cannot read symbolic link /proc/1/cwd: Permission denied
ls: cannot read symbolic link /proc/1/root: Permission denied
ls: cannot read symbolic link /proc/1/exe: Permission denied
and I can't find the init-process of the Debian-VPS in the spectator-context
or by the vps-tool. So, this entry in /proc is completely faked, I think.
In the old-style util-vserver-docu I found a flag "fakeinit". Does this exist
in the alpha-util-vserver also?
Well, I think this question is a typical newbie question, but I can't find the
-- Wilhelm Meier email: email@example.com _______________________________________________ Vserver mailing list Vserver@list.linux-vserver.org http://list.linux-vserver.org/mailman/listinfo/vserverReceived on Tue Jan 17 09:27:44 2006