Looking on the build server , /tmp seems to be filling up with files like
storage63942.tmp
storage63942.tmp.idx
hello58621world
Files26266562668.prj
Files26266562669.shp
and directories like
test47544kmz
shp_6762.tmp
Any chance we could make tests clean up after themselves ?
Could enable atime and install tmpwatch, but would prefer not to.
-Arne
--
Arne Kepp
OpenGeo - http://opengeo.org
Expert service straight from the developers
Arne Kepp ha scritto:
Looking on the build server , /tmp seems to be filling up with files like
storage63942.tmp
storage63942.tmp.idx
hello58621world
Files26266562668.prj
Files26266562669.shpand directories like
test47544kmz
shp_6762.tmpAny chance we could make tests clean up after themselves ?
We should make sure the tests do work inside /target of their
module, this was the mvn clean does the job for us.
However, we first have to identify which modules do generate
each of those pesky temp files.
I did a round of cleanup more than one year ago but some
other of these sillies have popped up...
Cheers
Andrea
--
Andrea Aime
OpenGeo - http://opengeo.org
Expert service straight from the developers.
Andrea Aime wrote:
Arne Kepp ha scritto:
Looking on the build server , /tmp seems to be filling up with files like
storage63942.tmp
storage63942.tmp.idx
hello58621world
Files26266562668.prj
Files26266562669.shpand directories like
test47544kmz
shp_6762.tmpAny chance we could make tests clean up after themselves ?
We should make sure the tests do work inside /target of their
module, this was the mvn clean does the job for us.
However, we first have to identify which modules do generate
each of those pesky temp files.
I did a round of cleanup more than one year ago but some
other of these sillies have popped up...
Did this include both geotools and geoserver? As far as I know most of the problem lies in geotools.
Cheers
Andrea
--
Justin Deoliveira
OpenGeo - http://opengeo.org
Enterprise support for open source geospatial.