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

Re: aircraft pullout

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: aircraft pullout
  • Date: Thu, 16 Feb 2006 12:58:30 -0700
Janet,

>Date: Thu, 16 Feb 2006 11:22:08 -0700
>From: Janet Scannell <address@hidden>
>To: Steve Emmerson <address@hidden>
>Subject: Re: aircraft pullout

The above message contained the following:

> Aircraft pullout is 12:30 for a 2 p.m flight.  That is definite now.

OK.  Right now, the computer on the plane is off-line:

    $ ping 600644362.tssmob.net
    ping: unknown host 600644362.tssmob.net

> I don't remember exactly what the message was.  It was something about 
> the fact that it could not connect to the host on the aircraft.  I could 
> change back to the old ldm code and test using that if you want.

Rather than doing that, I recommend sending a SIGUSR2 signal to the
downstream LDM process on Malbec to put it into verbose logging mode.

> Probably not at the time because when the aircraft is flying and we are 
> not getting data, it is usually a scramble to get things working again.  
> I can try these today.

OK.

Regards,
Steve Emmerson