NOTICE: This version of the NSF Unidata web site (archive.unidata.ucar.edu) is no longer being updated.
Current content can be found at unidata.ucar.edu.
To learn about what's going on, see About the Archive Site.
NOTICE: This version of the NSF Unidata web site (archive.unidata.ucar.edu) is no longer being updated.
Current content can be found at unidata.ucar.edu.
To learn about what's going on, see About the Archive Site.
Hi, Is there a way to have THREDDS systematically clean up uncompressed data files? We noticed that THREDDS can support compressed (gzip) NetCDF files, but the uncompressed files linger. A periodic program can be run to scan through and remove them, but this would assume that the periodic cleaning would keep up with the rate of uncompression as data is accessed. Maybe something similar to OPeNDAP Server 3 (dods_cache)? Even this has its limits. If the cache size is not high enough, with enough traffic, requests will get stomped. Or just a table in memory tracking uncompressed files. If the server/system ever crashed, then this would leave stuff about. We were wondering if the same compression support can be extended to include bzip2 compression (bz2)? Thanks! Rob -- Alaska Ocean Observing System Database Manager 907-474-7948 ============================================================================== To unsubscribe thredds, visit: http://www.unidata.ucar.edu/mailing-list-delete-form.html ==============================================================================
thredds archives: