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

Re: 20021125: pqing and pqact not writing to ldmd.log

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: 20021125: pqing and pqact not writing to ldmd.log
  • Date: Mon, 16 Dec 2002 09:22:02 -0700
Jeff,

>Date: Fri, 13 Dec 2002 15:45:56 -0500
>From: Jeff Ator <address@hidden>
>Organization: NOAA/NWS/NCEP
>To: Steve Emmerson <address@hidden>
>Subject: Re: 20021125: pqing and pqact not writing to ldmd.log

The above message contained the following:

> Thanks Steve! Yes, it does work now, so the new CPPFLAGS definitions
> do indeed seem to be what was needed!

Excellent!

> As a side note, I was initially taken aback when I saw entries in the
> LDM log that looked like:
> 
> Dec 13 18:34:02 s1n3 pqing[43608]:      379 20021213183402.927 FNEXRAD 682  
> SXUS08 KWAL 131800
> Dec 13 18:34:16 s1n3 pqact[30952]:      379 20021213183402.927 FNEXRAD 682  
> SXUS08 KWAL 131800
> 
> because we have always used NMC3 as our feedtype for non-binary data in both 
> pqing and pqact, and yet these data were now showing up in the logs as 
> FNEXRAD!?  But then I
> found the following snippet in the RELEASE NOTES for version 5.1.3:
> 
>                 Added "FNEXRAD" as the name for the NEXRAD floater
>                 feed type (FT13) and made the old name "NMC3" an alias
>                 for the same feed.
> 
> So I guess that would explain it, huh?  ;-)

Yup.  We're looking into ways to expand the number of feedtypes.

> Thanks again for your help!
> -Jeff

Our pleasure.

Enjoy the season,
Steve