Very Computer

Hi

essentially a new tru64 user. I have v5.1 732 alpha system.
My root file system is full and i want to delete the files present in
the /proc directory. When i try rm it tells me that this function not
implemented.

1) what does this mean
2) how do I delete the files in this directory
3) what are these files?

df -k output.

Filesystem          1024-blocks        Used   Available Capacity
Mounted on
root_domain#root         275176      268916          24   100%    /
/proc                         0           0           0   100%  
/proc
usr_domain#usr          1504880      382785     1101856    26%    /usr
usr_domain#var          1504880        6126     1101856     1%    /var
apps_dmn#apps           1469000      781342      679472    54%  
/apps
journal_dmn#journal     2325536        6408     2314360     1%  
/journal
data_dmn#data           8179376     4518873     3644032    56%  
/data
black:/system       6656648     4464597     2157520    68%    /system

files in /proc:

# ls
00000  00109  00269  00431  00531  00574  00593  00641  00703  00752
01047
00001  00119  00359  00520  00536  00575  00597  00645  00743  00769
01054
00068  00233  00363  00522  00540  00576  00630  00657  00744  00770
01175
00108  00268  00428  00530  00553  00582  00631  00676  00745  01046

thanks for your help
john

The /proc file system is not a real file system and does not use any
disk space. It can be mapped to obtain information about the currently
running processes.

Big H

Quote:>Hi

>essentially a new tru64 user. I have v5.1 732 alpha system.
>My root file system is full and i want to delete the files present in
>the /proc directory. When i try rm it tells me that this function not
>implemented.

>1) what does this mean
>2) how do I delete the files in this directory
>3) what are these files?

>df -k output.

>Filesystem          1024-blocks        Used   Available Capacity
>Mounted on
>root_domain#root         275176      268916          24   100%    /
>/proc                         0           0           0   100%  
>/proc
>usr_domain#usr          1504880      382785     1101856    26%    /usr
>usr_domain#var          1504880        6126     1101856     1%    /var
>apps_dmn#apps           1469000      781342      679472    54%  
>/apps
>journal_dmn#journal     2325536        6408     2314360     1%  
>/journal
>data_dmn#data           8179376     4518873     3644032    56%  
>/data
>black:/system       6656648     4464597     2157520    68%    /system

>files in /proc:

># ls
>00000  00109  00269  00431  00531  00574  00593  00641  00703  00752
>01047
>00001  00119  00359  00520  00536  00575  00597  00645  00743  00769
>01054
>00068  00233  00363  00522  00540  00576  00630  00657  00744  00770
>01175
>00108  00268  00428  00530  00553  00582  00631  00676  00745  01046

>thanks for your help
>john

The files in /proc are processes running on the system.  You don't
want to delete them even if you could.  Don't worry about that
particular file system being full, that's just the way it is.
You can find out more about the process file system by reading
the proc(4) manual page.

As for the root file system, some things to look for are:

o  files in /dev that are almost the same spelling as special
   device files, especially tape device names (new and old
   format).  The tape utilities will as easily create a regular
   file as open a device.  Spell the name wrong and you get a
   file.

o  Look for a "core" file in the root.  These are copies of a program's
   memory when it isn't working correctly and exits before it should.
   My recollection is that the first line of the output of strings(1)
   will be the name of the program.

o  This last is harder.  /tmp is often part of the root file system
   (it is on your system).  A file that was supposed to be temporary
   or is still open may be using the space.  Programs that use temporary
   files often remove the name after they open file.  When closed, the
   file is automatically deleted.  Unfortunately, this makes the file
   hard to see.  You may be able to use fuser or lsof to see what files
   are open on /tmp.

   If this is the problem, you might want to consider moving /tmp to
   its own file system.  You can give it as much space as you think
   it will need and fewer things are likely to be affected when it
   fills up.

Quote:

>df -k output.

>Filesystem          1024-blocks        Used   Available Capacity
>Mounted on
>root_domain#root         275176      268916          24   100%    /
>/proc                         0           0           0   100%  
>/proc
>usr_domain#usr          1504880      382785     1101856    26%    /usr

>files in /proc:

># ls
>00000  00109  00269  00431  00531  00574  00593  00641  00703  00752
>...
>thanks for your help
>john

--

Quote:> Hi

> essentially a new tru64 user. I have v5.1 732 alpha system.
> My root file system is full and i want to delete the files present in
> the /proc directory.

Don't! "procfs", for one has nothing to do with your ROOT file system being
full, and it cannot be deleted. Also, as you can see, it is *separate* file
system.

Quote:> When i try rm it tells me that this function not
> implemented.

> 1) what does this mean

Just what it says. ProcFS is a special file system which maps precesses adn
their memory maps to look like a file system, so they can be accessed with
de*s.

Quote:> 2) how do I delete the files in this directory

You don't. You can unmount it, if you do not wish to expose your processes
to de*s, but it won't save you a single byte of memory.

Quote:> 3) what are these files?

> df -k output.

> Filesystem          1024-blocks        Used   Available Capacity
> Mounted on
> root_domain#root         275176      268916          24   100%    /

ROOT file system, which is full. I'd check / and /tmp. And, yes, don't
forget /dev - if you see a particularly large file "nrmt0h" that that is it.

Quote:> /proc                         0           0           0   100%    /proc

ProcFS.

Quote:> usr_domain#usr          1504880      382785     1101856    26%    /usr
> usr_domain#var          1504880        6126     1101856     1%    /var

/var and /usr sharing usr_domain and looking good.

Quote:> apps_dmn#apps           1469000      781342      679472    54%    /apps
> journal_dmn#journal     2325536        6408     2314360     1%    /journal
> data_dmn#data           8179376     4518873     3644032    56%    /data

Another three AdvFS looking good, too.

Quote:> black:/system       6656648     4464597     2157520    68%    /system

NFS.

Quote:> files in /proc:

> # ls
> 00000  00109  00269  00431  00531  00574  00593  00641  00703  00752
> 01047
> 00001  00119  00359  00520  00536  00575  00597  00645  00743  00769
> 01054
> 00068  00233  00363  00522  00540  00576  00630  00657  00744  00770
> 01175
> 00108  00268  00428  00530  00553  00582  00631  00676  00745  01046

Processes.

Nix.