Ted Gervais wrote:
>
> On Tue, 24 Aug 1999, Maurice Hendrix wrote:
>
> > > In my /proc directory I have a bunch of files and they are nearly all '0'
> > > bit except one; and it is LARGE. Here is what I see (in part)..
> > >
> > > -r--r--r-- 1 root root 0 Aug 24 08:36 interrupts
> > > -r--r--r-- 1 root root 0 Aug 24 08:36 ioports
> > > -r-------- 1 root root 134221824 Aug 24 07:55 kcore
> > > -r-------- 1 root root 0 Aug 23 22:15 kmsg
> > > -r--r--r-- 1 root root 0 Aug 24 08:36 ksyms
> > >
> > > Kcore is over 134 megs large, and it really does occupy this much space.
> > > Does this appear normal. Why is this file so large? How do I reduce it or
> > > kill it? I tried booting things up with rescue disks and then deleted
> > > that file. I then rebooted normally and it was back. It just seems odd to
> > > have such a large file there which I never noticed before. And of course I
> > > would like to recover that drive space.
> > >
> > > Any thoughts?
> > >
> > AFAIK /proc is a virtual filesystem. Files in this filesystem are largely
> > none-existing. IIRC /proc/kcore is just an image. It does not occupy any
> > space on your disk.
> >
> > Anybody, please correct me if I'm wrong.
>
> That is what I thought; files in /proc dir are virtual files and do not
> occupy any real disk space. However, when I copied that file over to
> another directory I saw that it indeed was 134 megs large? HOw is that
> possible.
>
> --
> Ted Gervais <[EMAIL PROTECTED]>
> 44.135.34.254 gw.ve1drg.ampr.org
Except for the fact that it takes up no disk space it IS a real file.
It quacks like a duck. So what you have there is a physical copy of the
contents of RAM at the moment you copied. Delete the copy and leave the
original alone. Everything in the /proc filesystem is virtual and takes
up zero space. To prove this, do the following:
cd /proc
du
Note that du (diskusage) reports 0.
--
My public encryption key is available from
www.az.com/~drysdam/crypt/rysdam.gpg.html
and of course www.keyserver.net
