[LDM #EJF-472056]: LDM 6.13.0 released

Dave,

> It wasn’t just WXP scripts, either—those were just the most numerous and 
> visible. I have other scripts that launch runs of the WRF model every 6 
> hours, and with ldm-6.13.1.3, those WRF runs were all quickly aborted or 
> possibly not launched at all. Those scripts have one prominent thing in 
> common with virtually all of my WXP scripts—they run a WXP program called 
> “wxpfile”, which calculates UTC times that are offset by specified increments 
> (say, 6 hours or multiples of 6 hours) from a given UTC time. (For the last 
> six months I've been transitioning my many scripts to use the Unix “date” 
> command for this instead, but haven’t completed the transition yet.) I wonder 
> if the problems I saw with ldm-6.13.1.3 had something to do with date and 
> time handling?

I suspect the commonality of wxpfile(1) is just a coincidence. The changes I 
made dealt with the handling of UNIX file descriptors when creating a child 
process. The changes make the handling much more rigorous and robust.

I'll release 6.13.1 soon.

Thanks for all your help.

Regards,
Steve Emmerson

Ticket Details
===================
Ticket ID: EJF-472056
Department: Support LDM
Priority: Normal
Status: Closed
===================
NOTE: All email exchanges with Unidata User Support are recorded in the Unidata 
inquiry tracking system and then made publicly available through the web.  If 
you do not want to have your interactions made available in this way, you must 
let us know in each email you send to us.