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

Re: [Fwd: Re: 20000809: LDM feed?]

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: Re: [Fwd: Re: 20000809: LDM feed?]
  • Date: Thu, 31 Aug 2000 11:29:15 -0600
Pete Pokrandt wrote:
> 
> In a previous message to me, you wrote:
> 
>  >Hi Mark and Pete,
>  >
>  >I'm glad things are looking better for Mark.  I really like the way you guys
>   >worked that out.
>  >
>  >For internal reasons, I have been forwarding your recent correspondences to 
> R
>   >obb.  Please remove me from this thread and include address@hidden in
>   > any future messages.
>  >
> 
> Anne,
> 
> You've got it.. last one to you :)
> 
> Mark,  I have added cirrus.lsc.vsc.edu to my allow list for
> profhorn, to feed the SPARE|NMC2 feeds.
> 
> The spare feed is an older feed, and not much comes through on
> it anymore. To get the full conduit feed, request
> 
> SPARE|NMC2
> 
> from profhorn.meteor.wisc.edu.
> 
> Let me know if you have problems.
> 
> Pete
> 
> --
> +>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>+<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<+
> ^ Pete Pokrandt                    V 1447  AOSS Bldg  1225 W Dayton St^
> ^ Systems Programmer               V Madison,         WI     53706    ^
> ^                                  V      address@hidden       ^
> ^ Dept of Atmos & Oceanic Sciences V (608) 262-3086 (Phone/voicemail) ^
> ^ University of Wisconsin-Madison  V       262-0166 (Fax)             ^
> <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<+>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>

One last item for Mark before I'm outta here (for this thread, anyway)...

If connectivity is still a problem for you, take a look at the ldm program 
'netcheck'.  It does a ping and a traceroute to a variety of sites and reports 
the results back to a log file. It will also send email if there are packet 
losses above a certain threshold.  You can make it a cron job and test the 
network regularly.  This way you can at least record the problem, and possibly 
use it talk with your campus network administrators or your ISP.  Just a 
thought...

Anne
-- 
***************************************************
Anne Wilson                     UCAR Unidata Program            
address@hidden                 P.O. Box 3000
                                  Boulder, CO  80307
----------------------------------------------------
Unidata WWW server       http://www.unidata.ucar.edu/
****************************************************