[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

19991005: deleting old data

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.

  • Subject: 19991005: deleting old data
  • Date: Tue, 05 Oct 1999 14:28:40 -0600
>From: Tom Priddy <address@hidden>
>Organization: .
>Keywords: 199910052016.OAA10080

>From:  Tom Priddy
>
>We recently upgraded our sun workstations operating system to solaris 7.
>
>We have the ldm back up and online....but old data files are not being
>deleted. What crontab (or program) keeps file systems from filling up?
>ktp
>
>--
>============================================================
>Tom Priddy                                address@hidden
>Extension Ag. Meteorologist          ph:  606-257-3000ext245
>Ag. Weather Center                  fax:  606-257-5671
>243 Ag. Engineering Bldg
>Dept. of Biosystems and Ag. Engr.
>University of Kentucky
>Lexington, KY 40546-0276
>HOMEPAGE   http://wwwagwx.ca.uky.edu
>============================================================
>
>


Tom,

Your crontab probably used the ~ldm/bin/scour program (along with the
~ldm/etc/scour.conf) to periodically scour off old data. An example
for running the scour program every 3 hours using ldmadmin would look like:
0 1,4,7,10,13,16,19,22 * * * bin/ldmadmin scour >/dev/null 2>&1

Your ldm log files should also be rotated daily so they don't grow too 
large as well, eg: 00 17 * * * bin/ldmadmin newlog

Steve Chiswell