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.
>From: "James R. Frysinger" <address@hidden> >Organization: College of Charleston >Keywords: 200111061842.fA6Igt112242 LDM binary install Jim, >Got your afternoon/evening email but have been grading lab reports; my >mind is now mush. > >Just got this right before I logged off my home machine for the night. >I suppose it's the result of your work today. I can't fix it from here >because crontab -e calls up ed which doesn't display remotely on my >machine. (For some reason 'display metric.metricmethods.com:0' prior to >using 'crontab -e' gets blocked by my machine even though mcidas can >open it!) > >body { font-family: "times new roman" } p { font-size: 14pt } a { >color: #535378; text-decoration: none; }Output from "cron" command >From: sysadmin frysingj <address@hidden> (oper) >To: address@hidden > > >Your "cron" job on weather >bin/ldmadmin scour > >produced the following output: > >rm: ./nport is a directory >rm: ./nport/SOUNDER/14km is a directory >rm: ./nport/SOUNDER/20km is a directory This not an indication of a problem, but I tried to address it anyway. I changed the crontab entry to send all script output/error output to /dev/null. Nice, light touch, eh? :-) Tom