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.
Wenwu, > We are using ldm to transferring thousands files each day, but only a > very small portion of files crushed. I have attached a example: original > file (24HGAUGE.20060724.0800.gz.ori, good) and received file > (24HGAUGE.20060724.0800.gz.received). These two files have the same size > and they are binary files. > > This is the method I used to insert the files into ldm queue: > system "/home/ldm/bin/pqinsert -v -l /home/ldm/logs/ldmd.log -q > /home/ldm/data/ldm.pq -f WMO /path/file_name" > > I use following line at LDM client ldmd.conf file to get files: > REQUEST WMO ".*" 129.15.40.202 PRIMARY > > At pqact.conf files to write file (NO decoder used): > WMO > ^/home/gagecor/data/QPESUMS/conus/grid/([^/]*)/([^/]*)/([0-9A-Z]*.[A-Z]*.[0-9][0-9][0-9][0-9][0-1][0-9][0-3][0-9].[0-2][0-9][0-5][0-9]).gz > FILE -overwrite -close > /verif_data/input_data/conus/q2_gc/\1/\2/\3.gz > > Is there anything I can change? The above should work. I suspect that there's a problem with gzip(1) on your system. I'll investigate and will reply soon. Regards, Steve Emmerson Ticket Details =================== Ticket ID: QOQ-440372 Department: Support LDM Priority: Normal Status: Closed