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.
>From: yoksas <address@hidden> >Organization: UCAR/Unidata >Keywords: 200209071919.g87JJtj16814 LDM NIMAGE atm Hey, OK, so I feel like I am losing my mind. Friday afternoon, I commented out the allow for NIMAGE in atm's ldmd.conf file, and then I stopped the LDM and waited for a couple of minutes while I watched the load average on thelma. After noticing that it wasn't going down, I restarted the LDM on atm. Jeff was standing there so he should be able to verify this. My natural assumption was that feedme requests from ldm.meteo.psu.edu would then be denied, so I didn't bother to watch the LDM log file to see if ldm.meteo.psu.edu would connect up. A quick look at the ldmd.log file on atm this morning showed me that ldm.meteo.psu.edu IS feeding NIMAGE from atm. I verified this with a notifyme from shemp: /local/ldm% notifyme -vxl- -f NIMAGE -h ldm.meteo.psu.edu -o 3600 Sep 08 14:52:03 notifyme[6644]: Starting Up: ldm.meteo.psu.edu: 20020908135203.259 TS_ENDT {{NIMAGE, ".*"}} NOTIFYME(ldm.meteo.psu.edu) returns OK Sep 08 14:52:03 notifyme[6644]: NOTIFYME(ldm.meteo.psu.edu): OK Sep 08 14:52:03 notifyme[6644]: cdbf7e4c6f7560ec76ed1c2046fb65f7 12118349 20020908135753.683 NIMAGE 141171 sat/ch1/GOES-8/VIS/20020908 1345/EAST-CONUS/1km/ TIGE01 KNES 081345 Sep 08 14:52:03 notifyme[6644]: 44e53527570c58c34e5fdf2eb23fabb4 739660 20020908135803.977 NIMAGE 141172 sat/ch1/GOES-8/3.9/20020908 1345/EAST-CONUS/4km/ TIGE04 KNES 081345 I then verified that I did, in fact, comment out the allow on atm: atm.geo.nsf.gov.ldm> date Sun Sep 8 10:57:50 EDT 2002 atm.geo.nsf.gov.ldm> ls -lt ldmd.conf -rw-rw-r-- 1 ldm ustaff 4048 Sep 6 18:45 ldmd.conf atm.geo.nsf.gov.ldm> grep psu ldmd.conf allow ANY-NLDN-WSI ihlseng.ugems.psu.edu #allow NIMAGE ^[a-z].*\.meteo\.psu\.edu$ # Penn State University I then checked to make sure that ihlseng.ugems.psu.edu does not resolve to ldm.meteo.psu.edu: atm.geo.nsf.gov.ldm> nslookup ihlseng.ugems.psu.edu Server: twister.nsf.gov Address: 198.181.231.17 *** twister.nsf.gov can't find ihlseng.ugems.psu.edu: Non-existent host/domain So, ldmd.conf was modified at 18:45 (6:45 pm eastern time; 4:45 mountain time) as it should have been. Next, I looked at the LDM log file to make sure that I had stopped and restarted the LDM: atm.geo.nsf.gov.ldm> less ldmd.log Sep 6 18:48:45 atm.geo.nsf.gov ldm: [ID 702911 local0.info] LDM Start (login name, tty, login time, [from]): ldm pts/1 Sep 6 13:53 (shemp.u This line shows that 'ldm' started the LDM at 18:48:45 (6:48:45 pm) on Friday. This was done AFTER ldmd.conf was modified. So how in the world is ldm.meteo.psu.edu feeding NIMAGE from atm? Anne, given that NIMAGE has been fed to ldm.meteo.psu.edu right along, all comments/specualtions about whether the NIMAGE feed has pushed Penn State over the edge are invalid. I am bewildered to say the least! Tom -- +-----------------------------------------------------------------------------+ * Tom Yoksas UCAR Unidata Program * * (303) 497-8642 (last resort) P.O. Box 3000 * * address@hidden Boulder, CO 80307 * * Unidata WWW Service http://www.unidata.ucar.edu/* +-----------------------------------------------------------------------------+