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.
Doug, In a previous posting, you wrote > We have an allow any in our include file: > > ncepidp.conf:allow ANY 140.90.100.144 # vm-lnx-ncodf1.ncep.noaa.gov > ncepidp.conf:allow ANY 140.90.100.145 # vm-lnx-ncodf2.ncep.noaa.gov > ncepidp.conf:allow ANY 140.90.100.153 # vm-lnx-ncodfdev.ncep.noaa.gov Just FYI, the 3rd field of an ALLOW entry is a regular expression. As such, an unescaped period means "any character" rather than a period. It must be escaped with a backslash (e.g., "140\.90\.100\.153") to obtain what you want. Even better would be to anchor the beginning and end of the string (e.g., "^140\.90\.100\.153$") to eliminate any possibility of a mistaken match. This can't cause the problem you're seeing, however. I'd like to propose an experiment that can't possibly have any effect. Would you be so kind as to remove the in-line comment "# vm-lnx-ncodfdev.ncep.noaa.gov" from the relevant ALLOW entry and restart your LDM. Justin, Would you then please start your LDM (if it isn't already running) and also simultaneously execute the notifyme(1) and "ldmadmin watch" in two xterm(1)s as before. Let it run until you're certain that the LDM isn't receiving the products listed by the notifyme(1). Let me know if Hades has frozen over and this solves the problem. Regards, Steve Emmerson Ticket Details =================== Ticket ID: NDJ-862794 Department: Support LDM Priority: Normal Status: Closed