NOTICE: This version of the NSF Unidata web site (archive.unidata.ucar.edu) is no longer being updated.
Current content can be found at unidata.ucar.edu.

To learn about what's going on, see About the Archive Site.

Re: As you probably have seen by now...

Just had a chance to look at one of the systems here (where I'm most concerned with DDS|IDS, and we're not seeing the problem here, either. (sasquatch.tamu.edu)
Interesting problem. I hate tracking them when they don't fail the same on all systems... 

gerry

Pete Pokrandt wrote:

Steve Emmerson wrote:

Everyone,

I'm working on the problem.

--Steve Emmerson

Steve (and others)
For what it's worth, I've got two 6.6.3 machines here at UW-Madison (f5 and weather.aos.wisc.edu) that are NOT exhibiting this problem. All of my data so far as I can tell are being filed with the correct date. For example
DDS|IDS ^S[AP].* .... ([0-3][0-9])([0-2][0-9]) FILE /usr/local/ldm/data/weather/(\1:yy)(\1:mm)\1\2.METAR 
is filing correctly.
One is a Centos 4.4 x86_64 box and the other is a Red Hat Enterprise Linux AS release 3 (Taroon Update 8) 
Let me know if you'd like more details, or access to poke around.

Pete



Daryl Herzmann wrote:

On Thu, 31 May 2007, Harry Edmon wrote:
I am not seeing this. Are they being filed as 20070631, 20070701, or what? 

20070631 , it is happening here too with LDM 6.6.4 :(

daryl


--
Gerry Creager -- gerry.creager@xxxxxxxx
Texas Mesonet -- AATLT, Texas A&M University        
Cell: 979.229.5301 Office: 979.458.4020 FAX: 979.862.3983
Office: 1700 Research Parkway Ste 160, TAMU, College Station, TX 77843