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.
Larry, > I've tried four times in the past year to set up an ldm on my computer > to download wind files, without success. I'll be attending the LDM > training course in Boulder next week, where hopefully I can get some > problems solved. In the meantime I decided to make one more attempt to > get it running. > > Right now, the problem is with the items executed in the crontab file. > I set up the crontab file following the instructions at the following > URL: > > http://www.unidata.ucar.edu/software/ldm/ldm-6.8.1/basics/configuring.html#scour.conf > > The crontab file currently looks like: > > # m h dom mon dow command > 0 0 * * * bash -l -c 'bin/ldmadmin newlog' > 0 1,4,7,10,13,16,19,22 * * * bash -l -c 'bin/ldmadmin scour' > 0,5,10,15,20,25,30,35,40,45,50,55 * * * * bash -l -c 'bin/ldmadmin > addmetrics' > 0 0 * * * bash -l -c 'bin/ldmadmin newmetrics' > > I have also added my e-mail address to the .forward file in the ldm home > directory so that error messages are forwarded to my e-mail account. > > The problem is that these commands are somehow not being recognized when > executed by crontab, even though I can execute them in the ldm home > directory. > > For example, every five minutes I receive an e-mail crom the Cron Daemon > like the following: > > From: > Cron Daemon > <address@hidden> > To: > address@hidden > Subject: > Cron <ldm@phobos> bash -l -c > 'bin/ldmadmin addmetrics' > Date: > 10/25/2010 04:05:01 PM > > > expr: syntax error > > > But when I execute this command from the ldm home directory, I get no > error message: > > ldm@phobos:~$ bash -l -c 'bin/ldmadmin addmetrics' > ldm@phobos:~$ > > Do you have any thoughts on what the problem might be? Assuming you've set-up the LDM user as described in the documentation, then instead of entries like > 0 0 * * * bash -l -c 'bin/ldmadmin newlog' try 0 0 * * * bin/ldmadmin newlog > Thanks, > > Larry Mastin Regards, Steve Emmerson Ticket Details =================== Ticket ID: JYK-429101 Department: Support LDM Priority: Normal Status: Closed