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

Re: ldmprods in crontab

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: Re: ldmprods in crontab
  • Date: Wed, 18 Dec 2002 10:34:48 -0700 (MST)
On Tue, 17 Dec 2002, Patrick O'Reilly wrote:

> Has/does anyone run ldmprods  script through a cron job, and if so, could
> they share their crontab entry?  Not being a unix guru, can't figure out how
> to run it that way.  Seems best fit to run from command line.  Thanks in
> advance.


Patrick,

ldmprods was never meant to be run out of cron.  Since ldmprods runs
continuously, it would never terminate inside of the cron job. Also,
ldmprods takes a couple passes to get the output 100% correct.  That said,
if you are looking for a particular event to happen, one could look at the
*.stats files in the log directory. If you are motivated, you could use
mailpqstats script as a template especially the ldmstats routine to
extract the info you are looking to investigate. The output could be made
into a batch mode so then you could put the script in the cron.

Hope this helps,
Robb...





> 
> Patrick
> _______________________________________
> Patrick O'Reilly
> Meteorological Decision Support Scientist
> The STORM Project - University of Northern Iowa
> address@hidden  ~  ph: 319-273-3789
> 
> 

===============================================================================
Robb Kambic                                Unidata Program Center
Software Engineer III                      Univ. Corp for Atmospheric Research
address@hidden             WWW: http://www.unidata.ucar.edu/
===============================================================================