Re: odd characters in CONDUIT filenames

David,

That may mean that the string is not null terminated from the library
routine that 
creates the parameter id. I'll check into it.

Steve Chiswell
Unidata User Support


On Tue, 2006-11-28 at 15:26 -0600, David Wojtowicz wrote:
> I’m occasionally seeing some odd non-ASCII characters in the !...!
> part of the filename in various CONDUIT products: 
> 
>  
> 
> Here’s one example: (it occurs in other places too)
> 
>  
> 
> notifyme -f CONDUIT -p 'CPRXX' -v –l /dev/tty  -o 3000
> 
>  
> 
> Nov 28 21:22:07 notifyme[25733] INFO:    14378 20061128205052.834
> CONDUIT 169  d
> 
> ata/nccf/com/nam/prod/nam.20061128/nam.t18z.awip1278.tm00.grib2 !
> grib2/ncep/NAM_
> 
> +/0 - NONE! 00016900F078/CPRXX
> 
> Nov 28 21:22:08 notifyme[25733] INFO:    13301 20061128205205.682
> CONDUIT 169  d
> 
> ata/nccf/com/nam/prod/nam.20061128/nam.t18z.awip1281.tm00.grib2 !
> grib2/ncep/NAM_
> 
> 84/#000/200611281800F081/CPRXXêO¯*/0 - NONE! 000169
> 
> Nov 28 21:22:09 notifyme[25733] INFO:    13414 20061128205337.547
> CONDUIT 169  d
> 
> ata/nccf/com/nam/prod/nam.20061128/nam.t18z.awip1284.tm00.grib2 !
> grib2/ncep/NAM_
> 
> 84/#000/200611281800F084/CPRXXÛs}+/0 - NONE! 000169
> 
>  
> 
>  
> 
> -----
> David Wojtowicz, Sr. Research Programmer, Sysadmin
> Dept of Atmospheric Sciences / Computer Services
> University of Illinois at Urbana-Champaign
> address@hidden  (217) 333-8390
> 
> 
>  
> 
> 
-- 
Steve Chiswell <address@hidden>
Unidata