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.
Mark, > > String-replacement based on data-product creation-time uses the strftime(3) > > function and, unfortunately, calling that function with a "%N" conversion > > specification is non-standard and will result in undefined behavior on some > > systems. > > > Yes, this is unfortunate. If my system's strftime() function supports > the %N, then will LDM also support it automatically? If your strftime() supports "%N", then you should be able to use it now. > > Are the product-identifiers of the data-products in question not > > sufficiently unique that you can't create unique pathnames? > > > That is correct. Occasionally, we will get so many small products in a > burst that even though they don't arrive consecutively, they *do* still > arrive within the same clock second and thus not be unique. We get > around this by piping the contents through a script which adds a `date > +%N` to the back of the filename to ensure uniqueness. This work-around > suffices for now, but we had to work at it to make it efficient enough > not to increase the system's load average. > > Mark Regards, Steve Emmerson Ticket Details =================== Ticket ID: DZH-705263 Department: Support LDM Priority: Normal Status: Closed