[McIDAS #XRR-599672]: Configuring scouring of McIDAS data

Hi Samuel,

re:
> I ended putting a crontab entry in our current machine that uses
> 
> "find /data/ldm/mcidas/grib -name "*" -atime +11 -print -exec rm -f {} \;"
> 
> We have a new machine to install, and I was wondering if there is any way
> to avoid this kind of problem with our new machine?

The problem being files that are created by McIDAS-XCD with dates in the name
that are in the future?  If yes, then the _real_ solution is for me or SSEC to
figure out how to trap impossible names (names with dates far in the future)
and discard the GRIB message accordingly.

There is a new McIDAS-X version from SSEC, v2008, that I am now working on
for a Unidata release.  I will see if SSEC has addressed this problem in the
new XCD portion of the code.

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: XRR-599672
Department: Support McIDAS
Priority: Normal
Status: Closed