This archive contains answers to questions sent to Unidata support through mid-2025. Note that the archive is no longer being updated. We provide the archive for reference; many of the answers presented here remain technically correct, even if somewhat outdated. For the most up-to-date information on the use of NSF Unidata software and data services, please consult the Software Documentation first.
Hi Martha, re: > We have noticed that if LDM runs on our NOAAPORT decoder for several > days, the file system where the data are being written begins to fill > up, not just with data files but seemingly with large temporary files, > scratch files, etc. We found this out when restarting LDM dropped > the file system usage back a good bit. Our experience with situations like the one you are describing have all been associated with users deleting files that are open for writing by a routine running in the LDM process group. Even though the file(s) may look like they get deleted, they aren't really until the LDM is stopped. > Is there a recommendation in place about restarting LDM periodically to > clean out these files? No, the recommendation is to review your setup (e.g., cron-initiated scouring of some sort) to find the process(es) that may be deleting files that are being held open. > Thanks. No worries. Cheers, Tom -- **************************************************************************** Unidata User Support UCAR Unidata Program (303) 497-8642 P.O. Box 3000 address@hidden Boulder, CO 80307 ---------------------------------------------------------------------------- Unidata HomePage http://www.unidata.ucar.edu **************************************************************************** Ticket Details =================== Ticket ID: WDB-706909 Department: Support LDM Priority: Normal Status: Closed