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

20010216: 7.704 upgrade and NEXRAD ADDE configuration (cont.)

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: 20010216: 7.704 upgrade and NEXRAD ADDE configuration (cont.)
  • Date: Fri, 16 Feb 2001 10:51:07 -0700
>From: Gilbert Sebenste <address@hidden>
>Organization: NIU
>Keywords: 200102151852.f1FIq6L29876 McIDAS-X 7.704 NEXRAD NOWrad

Gilbert,

re: I made the changes
>OK. Glad I'm not loopy! Oh, wait. From the medicine. Riggghhht. :-)

re: problem with RedHat 6.x,7.x and ADDE sounding servicing
>Well, the 2.4 kernel from Redhat is coming out in a few weeks, according
>to the website. Maybe it will fix itself?

Nope, we have already tried (inadvertantly) the 2.4 kernel (beta) on
a machine at UNC Ashville.

re: you not having setup NEXRAD ADDE services yet
>Yep!

re: setup NEXRAD and NOWrad (tm)
>Ummm...wait a minute. *Who* can access my NOWrad(tm) data? I don't want
>the whole world getting at that...how do I control this?

To control the set of users that are allowed access to the RTNOWRAD
data, you should edit ~mcidas/NIUNOWR.CFG and

change:

IPMASK=*

to:

IPMASK=pattern

For instance, if you wanted to allow all machines from the 128.117.140
subdomain (Unidata :-), you would set IPMASK to:

IPMASK=128.117.140.*

etc.

re: how to check access to your own data.
>OK.

re: Hope you don't mind the mods...
>Someone logging in to do an improvement on my machine? Someone awesome?
>Hey, you'll get no complaints from the peanut gallery here! :-) Thanks
>Tom! All your help is *greatly* appreciated!!!

You are welcome.  Please let me know if you run into anything unexpected.

Tom