Re: CVS commit: basesrc

[Thilo Manske <Thilo.Manske%HEH.Uni-Oldenburg.DE@localhost>]

On Tue, Mar 07, 2000 at 11:30:47PM +0900, Noriyuki Soda wrote:
> > > I don't know about "most people", but I tend to use -s=<half-phys-mem>
> > > for sizing an MFS /tmp, and make sure /var (which is always on a
> > > separate partition) is large enough to hold two crash dumps (ie, 2 x
> > > phys-mem).
      (+2*size of kernel image)

I have a symlink from /var/crash to somewhere else; 260MBytes of disc space
is not that much these days, but I prefer to have it allocated somewhere
I can make better use of it (eg. in /usr or /home instead of /var where it
rotts unused most of its time)

> > So, there are many aspects. :-(
Yes, there are :-)

...

> In my system, MFS /tmp (32MB) cannot hold temporary files for locate
> database, but /var/tmp (150MB) can.
Well, since nearly nothing except vi uses /var/tmp in the proper way
(i.e. for stuff that may be of need for longer than a few minutes)
my /tmp has about twice as much space free as my /var/tmp, e.g.

Filesystem  1K-blocks     Used    Avail Capacity  Mounted on
mfs:179         38663        1    36728     0%    /tmp
/dev/wd1a       22903     6057    15700    27%    /var

The fact that weekly repeatedly fails on two of my systems because of
this "inspired" me to look into the source and submit the change request.

> I think historically it is recommended to make size of /var/tmp larger
> than size of /tmp. And I always do this setting.
Out of curiosity: When & where was this recommended?

> How about back out the commitment?
Most programs (tar, pax, compiler stuff, many, many packages - nearly
everything except updateddb.csh?) use /tmp as default to store their
temporary files---often larger than the average stuff updatedb.csh
creates---so those programs should be changed to use /var/tmp then as well,
shouldn't they?

...

IMHO we really should not talk about sizes here.
"Size doesn't matter" :-)

Nobody should make asumptions about the size of /tmp or /var/tmp,
i.e. wich of the two has more free space. It's about purpose:
Store temporary stuff you will need after the next [re]boot in /var/tmp
and everything else in /tmp. (At least this is how I understand hier(7))

So (IMHO) updatedb.csh really should use /tmp - if this doesn't work for
some user [s]he will have to adjust the size of /tmp or set TMPDIR (e.g. in
weekly.conf) to something else - as [s]he has to do with every other program.

Now stone me :-)
-- 
Dies ist Thilos Unix Signature! Viel Spass damit.