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.
Hi Martha, re: > Here you go...what I did was replace "data/nexrad" with "/data/nexrad" > so perhaps I left out some sort of control character? OK, I don't see anything amiss in the action. The only thing left is /data/nexrad would not seem to be writable by the user running the LDM (even though you have assured me that it is). This is assuming, of course, that the NEXRAD3 products are still being received by noaaportxcd. Here is what I would do if I had login to your machine as 'ldm'. - login as 'ldm' (not sudo, not 'su ldm') - ls -alt /data/nexrad - id ldm - touch /data/nexrad/xxx <- verify write permission - notifyme -vl- -f NEXRAD3 As soon as you see a NEXRAD3 product being received, check to see where it has been written. Any chance of me getting a login? 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: IWJ-443798 Department: Support McIDAS Priority: Normal Status: Closed