That look to be the case, thanks guys and happy holidays!
Ray
On Thursday, December 23, 2010 3:34pm, "Jeff Lake - Admin"
<admin@xxxxxxxxxxxxxxxxxxxx> said:
> yep I see it now...
> my main L2 server also reject's older then 10,
> just opened it up to my GEMPAK machine and there it is ..
> real old but there
>
> -Jeff
>
>
>
>> On Thu, 23 Dec 2010, admin@xxxxxxxx wrote:
>>
>>> It may be void,but not null:
>>>
>>> [ldm@wsr88d ~]$ ldmadmin watch -f NEXRAD2
>>> (Type ^D when finished)
>>> Dec 23 20:15:44 pqutil INFO: 19395 20101223195236.907 NEXRAD2 77044
>>> L2-BZIP2/KENX/20101223194709/77/44/I/V03/0
>>> Dec 23 20:15:46 pqutil INFO: 19180 20101223195244.984 NEXRAD2 77045
>>> L2-BZIP2/KENX/20101223194709/77/45/I/V03/0
>>> Dec 23 20:15:48 pqutil INFO: 69460 20101223195246.028 NEXRAD2 57010
>>> L2-BZIP2/KOKX/20101223195057/57/10/I/V03/0
>>
>> He's right, Jeff. I see what is happening now. My LDM only grabs level 2
>> data files that are newer than 10 minutes, to prevent a monster data dump
>> into my work and Allisonhouse systems. It's delayed by 24 minutes. So, my
>> systems are rejecting the delayed data as too old. And that backs up what
>> WSI et al are seeing. It's coming in, just significantly delayed.
>>
>> *******************************************************************************
>> Gilbert Sebenste ********
>> (My opinions only!) ******
>> Staff Meteorologist, Northern Illinois University ****
>> E-mail: sebenste@xxxxxxxxxxxxxxxxxxxxx ***
>> web: http://weather.admin.niu.edu **
>> *******************************************************************************
>
