From: Jacques Gelinas (jack_at_solucorp.qc.ca)
Date: Tue Jan 22 2002 - 22:58:17 EST
On Tue, 22 Jan 2002 12:50:51 -0500, Dave Cost wrote
> > One of the things that I've noticed is that running du -s * in the vserver
> > directory results in running vservers showing massive /proc directories. A
> > 500mb vserver install seems to take up 1.5Gb.
>
> The /proc directory does not take any space. It's a virtualization of some
> kernel structures which includes the whole kernel memory, thus the big size.
One of the big virtual component is /proc/kcore, which represent the
physical ram of the server. For (obvious) security reason, a vserver is not
allowed to open that file (controlled by CAP_SYS_ADMIN). So since
a vserver is not allowed to read it, it won't be part of the new vproc file system.
In a sens, vproc will solve that bug, which is not really one. I remember
one of my friend who was trying to save some disk space. He was trying
to get rid of /proc/kcore and could not. What a deception when he learned
that there were no way to unlink that file and that, anyway, it would not
save a single byte on disk :-)
---------------------------------------------------------
Jacques Gelinas <jack_at_solucorp.qc.ca>
vserver: run general purpose virtual servers on one box, full speed!
http://www.solucorp.qc.ca/miscprj/s_context.hc
This archive was generated by hypermail 2.1.4 : Mon Aug 19 2002 - 12:01:00 EDT