[STATSGRASS] propagating temporary files

[Hamish]

> I seem to be getting propagating temporary files that belong to GRASS 
> in both the GRASS database mapset .tmp directory and R's /tmp  
> directory. For example,

modules should clean up their messes, yes. Can you isolate what's
leaving stuff behind?

--> check that some part of the tool chain isn't failing. The easiest
way to get lots of .tmp files is for a module to exit with an error
before it gets to the cleanup code at the end of the program.

e.g. in a script:

g.module
if [ $? -ne 0 ] ; then
  echo "an error occured"
  exit 1
fi


> Neither are deleted once command line code is executed, as should be  
> the case from my understanding.

Yes. Modules should be self-contained.

> Since I am running lots of simulations this quickly junks up available
> disk space, and I believe is contributing to a slow down in
> performance.

It's not good, but I don't think it will slow down performance much
unless the disk is near full.

> I can disappear these files at run-time, but the strange thing is that
> this didn't appear to be a problem a couple of a weeks ago.

usually $GISBASE/etc/clean_temp is run at GRASS startup and exit to
flush the $MAPSET/.tmp/ dir. At your own risk you can call it within
your GRASS session to clean out the muck.

> Any suggestions before I reinstall both softwares and packages?

I doubt that will help much unless you would do a version upgrade.


Hamish