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.
On Wed, 28 Mar 2001, Jeff Weber wrote: > Hi Neil, > > Yes, pluto must request DIFAX from their upstream host. > > I am getting no response from ANYONE at FSU. > > I did restrict your feed from thelma to DIFAX, but can change that to > ANY-WSI > > if FSU is not working for you currently. > > I have contacted pluto's upstream host to insure an allow is in > place..also no word, i suspect many people are on break. > > If you hear from Bill please have him send a copy of his ldmd.conf file > to us and we will figure this out, i will try to contact pluto's upstream > again as well, tho i suspect pluto's "allows" are wide open. > > > -Jeff > ____________________________ _____________________ > Jeff Weber address@hidden > Unidata Support PH:303-497-8676 > NWS-COMET Case Study Library FX:303-497-8690 > University Corp for Atmospheric Research 3300 Mitchell Ln > http://www.unidata.ucar.edu/staff/jweber Boulder,Co 80307-3000 > ________________________________________ ______________________ > > On Tue, 27 Mar 2001, Neil R. Smith wrote: > > > Jeff Weber wrote: > > > > > > Hi Neil, > > > > > > The best way to check would be with a: > > > notifyme -vl - -h pluto.met.fsu.edu > > > > > > If you get any info you know you are allowed for access. > > > > > > There is no way to determine what you are allowed for other than asking > > > the admin, or viewing their logs or ldmd.conf file > > > > Well, when I do this to pluto I get: > > coriolis{ldm}7% notifyme -v -l - -h pluto.met.fsu.edu > > Mar 27 22:21:54 notifyme[19984]: Starting Up: pluto.met.fsu.edu: > > 20010327222154.206 TS_ENDT {{ANY, ".*"}} > > Mar 27 22:21:54 notifyme[19984]: NOTIFYME(pluto.met.fsu.edu): reclass: > > 20010327222154.206 TS_ENDT {{FSL2|MCIDAS|IDS|HDS|DDPLUS, ".*"}} > > Mar 27 22:21:54 notifyme[19984]: NOTIFYME(pluto.met.fsu.edu): OK > > Mar 27 22:21:56 notifyme[19984]: 5579 20010327222156.726 HDS > > 052 SDUS88 > > [...] > > > > When I do this to thelma I get: > > coriolis{ldm}8% notifyme -v -l - -h thelma.unidata.ucar.edu > > Mar 27 22:22:58 notifyme[19987]: Starting Up: thelma.unidata.ucar.edu: > > 20010327222258.334 TS_ENDT {{ANY, ".*"}} > > Mar 27 22:22:58 notifyme[19987]: NOTIFYME(thelma.unidata.ucar.edu): > > reclass: 20010327222258.334 TS_ENDT {{DIFAX, ".*"}} > > Mar 27 22:22:58 notifyme[19987]: NOTIFYME(thelma.unidata.ucar.edu): OK > > > > The 'Starting Up' line to pluto looks like their allow info while the > > reclass line looks like it my be our request item list - except that > > our request list includes a request for DIFAX (on a line by itself) > > as I've forwarded to you previously. > > > > But the reclass line to thelma suggests that what is shown is the > > allow to coriolis which is restricted to DIFAX. > > > > Can you explain this? Comparing the two notifyme's I'd say pluto still > > isn't config'd to send me DIFAX. > > > > BTW, Bill Cottrill emailed me yesterday to check the difax again since > > he redid something on his pluto end of things. The difax still is not > > being ingested here. > > -Neil > > -- > > Neil R. Smith, Comp. Sys. Mngr. address@hidden > > Dept. Atmospheric Sci., Texas A&M Univ. 979/845-6272 FAX:979/862-4466 > > > >