[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[LDM #EAQ-733441]: notifyme utility

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.

  • Subject: [LDM #EAQ-733441]: notifyme utility
  • Date: Tue, 08 Nov 2016 16:08:13 -0700
Erik,

According to 
<http://www.unidata.ucar.edu/software/ldm/ldm-current/basics/behavior.html#upstream>,
the first relevant ALLOW entry determines what the downstream LDM (i.e., the
notifyme(1) process) is allowed to receive.

Try moving the "allow ANY" to before the "allow WMO".

> I was using notifyme to see incoming data that match in pqact in our
> downstream server.  Upon closer examination of ldmd.conf we have the
> following entries.  It looks like WMO was overriding ANY.  Can you think of
> any reason why these might be necessary?
> 
> # send anything to your own machine
> allow   WMO
> ^((localhost|loopback)|(127\.0\.0\.1\.?$)|(.*\.[a-z].*\.noaa\.gov\.?$))
> #
> allow   ANY
> ^((localhost|loopback)|(127\.0\.0\.1\.?$)|(.*\.[a-z].*\.noaa\.gov\.?$))

Regards,
Steve Emmerson

Ticket Details
===================
Ticket ID: EAQ-733441
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.