files recovery after rm?

[Conor P. Cahill]

In article <7444 at sdcsvax.UCSD.Edu>, mikulska at odin.ucsd.edu (Margaret Mikulska) writes:
> In article <20551 at unix.cis.pitt.edu> yahoo at unix.cis.pitt.edu (Kenneth L Moore) writes:
> >In article cpcahil at virtech.uucp (Conor P. Cahill) writes:
> >
> >==>Also, since /tmp is frequently used by lots of programs, leaving files in
> >==>those directories for a long period of time will result in the size of the 
> >==>directory growing and can have a significant 
> >==>performance impact on the entire system.
> 
> The main impact is not that much performance, but 'file system full' and
> 'no space on device', especially when /tmp is not on a separate disk

Try putting 3 or 5 thousand files on /tmp and see the overall impact 
it has on the system (performance wise).  You will probably be quite
suprised.  Each time a program tries to create a file on /tmp the kernel
must read the entire directory until it finds the first free slott and 
as time goes on, the long term files (like those placed by an unfriendly rm
alias) will tend to take up the slots at the start of the directory file, so
the kernel will tend to have to read the entire directory EVERY time someone
opens, create, or removes a file in that directory.

Since /tmp is accessed by lots of programs (like some shells, vi, cc, ar, etc)
this can have a tremendous performance inpact on your system.

What you say about space is correct and is also a major consideration.

-- 
+-----------------------------------------------------------------------+
| Conor P. Cahill     uunet!virtech!cpcahil      	703-430-9247	!
| Virtual Technologies Inc.,    P. O. Box 876,   Sterling, VA 22170     |
+-----------------------------------------------------------------------+