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: Eirh-Yu Hsie <address@hidden> >Organization: CU/CIRES NOAA/ESRL >Keywords: 200512091601.jB9G1w7s009532 McIDAS Solaris 10 Hi Hsie, re: How did you setup the Solaris 10 services on hail? >I use Solaris 10 utility "inetconv" to convert inetd.conf line to xml >file. Then use "svccfg" to import the xml file into smf service. OK. >The >conversion utility (inetconv) seems not do the conversion correctly (see >the attached file, lines 33, 38 and 39). Hmm... The version of mcidas-tcp.xml you sent me does not look like the one currently on hail. Here is what I think is the the difference: copy you sent: <exec_method type='method' name='inetd_start' exec='/home/mcidas/solaris/bin/mcservsh /home/mcidas' timeout_seconds='0'> <method_context> <method_credential user='mcadde' group='unidata' /> </method_context> <propval name='arg0' type='astring' value='-H' /> </exec_method> copy currently on hail: <exec_method type='method' name='inetd_start' exec='/home/mcidas/solaris/bin/mcservsh -H /home/mcidas' timeout_seconds='0'> <method_context> <method_credential user='mcadde' group='unidata' /> </method_context> </exec_method> Since the timestamp on the file (/var/svc/manifest/network/mcidas-tcp.xml) was updated this morning: ls -alt /var/svc/manifest/network/mcidas-tcp.xml -rw-r--r-- 1 root other 2317 Dec 12 10:44 /var/svc/manifest/network/mcidas-tcp.xml Question: I assume that you either edited the XML files or reran inetconv, true? If yes, I need to retry the remote ADDE access without the modifications I made to ~mcidas/solaris/bin/mcservsh. Please advise >From address@hidden Mon Dec 12 13:19:54 2005 re: >Please negect my previous message. I can find the data if I login as >mcidas: >hail:[115]% dataloc.k LIST >Group Name Server IP Address >-------------------- ---------------------------------------- >AMRC UWAMRC.SSEC.WISC.EDU >BLIZZARD HAIL.AL.NOAA.GOV >CIMSS HAIL.AL.NOAA.GOV >GINICOMP HAIL.AL.NOAA.GOV >GINIEAST HAIL.AL.NOAA.GOV >GINIWEST HAIL.AL.NOAA.GOV >GOESEAST HAIL.AL.NOAA.GOV >ME7 IO.SCA.UQAM.CA >MYDATA <LOCAL-DATA> >NEXRCOMP HAIL.AL.NOAA.GOV >RTGRIDS HAIL.AL.NOAA.GOV >RTIMAGES HAIL.AL.NOAA.GOV >RTNEXRAD HAIL.AL.NOAA.GOV >RTPTSRC HAIL.AL.NOAA.GOV >RTWXTEXT HAIL.AL.NOAA.GOV >TOPO HAIL.AL.NOAA.GOV ><LOCAL-DATA> indicates that data will be accessed from the local data >directory.DATALOC -- done >hail:[116]% dsserve.k LIST RTGRIDS >Group/Descriptor Type Format & Range RT Comment >------------------------ ----- ------------------ -- -------------------- >RTGRIDS/ALL GRID GRID 5001-6210 Y Real-Time Grids >RTGRIDS/AVN GRID GRID 5701-5900 Y Real-Time AVN Grids >RTGRIDS/ECMWF GRID GRID 5251-5260 Y Real-Time ECMWF Grids >RTGRIDS/ETA GRID GRID 5501-5620 Y Real-Time ETA Grids >RTGRIDS/GFS GRID GRID 5701-5900 Y Real-Time GFS/AVN Grids >RTGRIDS/MDR GRID GRID 5301-5310 Y Real-Time MDR/AVN Grids >RTGRIDS/MISC GRID GRID 5001-5010 Y Other Real-Time Grids >RTGRIDS/MRF GRID GRID 5701-5900 Y Real-Time MRF Grids >RTGRIDS/MRF-UW GRID GRID 101-110 MRF Grids in UW stream >RTGRIDS/NAM GRID GRID 5501-5620 Y Real-Time NAM Grids >RTGRIDS/NGM GRID GRID 5051-5090 Y Real-Time NGM Grids >RTGRIDS/NGM-UW GRID GRID 1-10 NGM Grids in UW stream >RTGRIDS/RUC GRID GRID 5201-5280 Y Real-Time RUC Grids >RTGRIDS/UKMT GRID GRID 6101-6210 Y Real-Time UK Met Grids >dsserve.k: done >hail:[118]% whoami >mcidas The DSSERVE command (dsserve.k) will list out how a dataset is configured, not what is in a dataset. I think you meant to run the DSINFO command instead of DSSERVE: dsinfo.k IMAGE RTIMAGES imglist.k RTIMAGES/GE-IR etc. >But I can not get anything as an end user: >hail:[124]% whoami >hsie >hail:[125]% dataloc.k LIST >Group Name Server IP Address >-------------------- ---------------------------------------- >AMRC UWAMRC.SSEC.WISC.EDU >BLIZZARD HAIL.AL.NOAA.GOV >CIMSS 140.172.240.150 >FLXP 140.172.240.167 >GINICOMP 140.172.240.150 >GINIEAST 140.172.240.150 >GINIWEST 140.172.240.150 >GOESEAST HAIL.AL.NOAA.GOV >ME7 IO.SCA.UQAM.CA >MYDATA <LOCAL-DATA> >NEXRCOMP 140.172.240.150 >RTGRIDS 140.172.240.150 >RTIMAGES 140.172.240.150 >RTNEXRAD 140.172.240.150 >RTPTSRC 140.172.240.150 >RTWXTEXT 140.172.240.150 >TOPO 140.172.240.150 ><LOCAL-DATA> indicates that data will be accessed from the local data >directory. >DATALOC -- done >hail:[126]% dsserve.k LIST RTGRIDS >Group/Descriptor Type Format & Range RT Comment >------------------------ ----- ------------------ -- -------------------- >dsserve.k: done >hail:[127]% Two things here: - the GOESEAST dataset is only found on the machine unidata2.ssec.wisc.edu - I believe you want to run the DSINFO command: dsinfo.k IMAGE RTIMAGES imglist.k RTIMAGES/GE-IR etc. Question: is 140.172.240.150 the current IP address for hail? Cheers, Tom -- 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.