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.
John, > I only just started the command a few minutes ago, but we are starting to > fall behind on our images. > > ldm@mammatus:~$ notifyme -vl- -f NEXRAD3 > 20190828T183800.329787Z notifyme[30769] NOTE notifyme.c:385:main() Starting > Up: localhost: 20190828183800.329658 TS_ENDT {{NEXRAD3, ".*"}} > 20190828T183800.329824Z notifyme[30769] NOTE ldm5_clnt.c:460:forn5() LDM-5 > desired product-class: 20190828183800.329658 TS_ENDT {{NEXRAD3, ".*"}} > 20190828T183800.330089Z notifyme[30769] INFO error.c:236:err_log() Resolving > localhost to 127.0.0.1 took 0.000235 seconds > 20190828T183800.450894Z notifyme[30769] NOTE ldm5_clnt.c:294:forn_signon() > NOTIFYME(localhost): OK The above doesn't show a product latency. Did it not print anything after the "OK"? Are you starting a lot of processing on that host at 18Z? It would help if we could log onto the system as the LDM user. Is this possible? Regards, Steve Emmerson Ticket Details =================== Ticket ID: GUQ-669331 Department: Support LDM Priority: Normal Status: Closed =================== NOTE: All email exchanges with Unidata User Support are recorded in the Unidata inquiry tracking system and then made publicly available through the web. If you do not want to have your interactions made available in this way, you must let us know in each email you send to us.