[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[LDM #LRD-467349]: Request to allow HRRR feed
- Subject: [LDM #LRD-467349]: Request to allow HRRR feed
- Date: Wed, 25 Jun 2014 16:17:53 -0600
Hi Evan,
re:
> I followed your instructions below and ran:
>
> [ldm@frtt1 ~]$ notifyme -vl- -f EXP -h hrrr.unidata.ucar.edu
> Jun 25 22:07:04 notifyme[24747] NOTE: Starting Up:
> hrrr.unidata.ucar.edu: 20140625220704.615 TS_ENDT {{EXP, ".*"}}
> Jun 25 22:07:04 notifyme[24747] NOTE: LDM-5 desired product-class:
> 20140625220704.615 TS_ENDT {{EXP, ".*"}}
> Jun 25 22:07:04 notifyme[24747] INFO: Resolving hrrr.unidata.ucar.edu to
> 128.117.156.16 took 0.004217 seconds
> Jun 25 22:07:04 notifyme[24747] NOTE: NOTIFYME(hrrr.unidata.ucar.edu): OK
Oops. I meant to test the FSL2 feed, not EXP; my bad. This is the
correct 'notifyme' invocation to test the ALLOW:
notifyme -vl- -f FSL2 -h hrrr.unidata.ucar.edu
The example ~ldm/etc/ldmd.conf REQUEST line I included in the previous email
was/is correct:
request FSL2 "^(WRFPRS|GRIB2)" hrrr.unidata.ucar.edu
NB: the FSL2 feed contains more than just HRRR data, hence the regular
expression pattern "^(WRFPRS|GRIB2)" instead of a blanket everything ".*"!
re:
> I see nothing else; the terminal appears to be waiting for something. Is
> this/What is the desired response to those commands?
No, my bad. I run 'notifyme' so often testing the EXP feed, that my
fingers incorrectly "did the walking" in my earlier reply. Again, I
apologize!
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: LRD-467349
Department: Support IDD
Priority: Normal
Status: Closed
