[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[LDM #QLM-179324]: Bug in LDM 6.7.0.0 (and previous?)

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.

  • Subject: [LDM #QLM-179324]: Bug in LDM 6.7.0.0 (and previous?)
  • Date: Thu, 13 Mar 2008 10:56:23 -0600
Gilbert,

> BTW, I see this when I typoe "ldmadmin" in 6.7.0.0:
> 
> options:
> -v              Turn on verbose mode
> -x              Turn on debug mode (includes verbose mode)
> -c              Clobber an exisiting product queue
> -m maxLatency   Conditional data-request temporal-offset
> -o offset       Unconditional data-request temporal-offset
> -q q_path       Specify a product queue path
> LDM Default: /dev/shm/ldm.pq
> pqsurf Default: /dev/shm/pqsurf.pq
> 
> Shouldn't that be "-Q" instead of "-q"?

Possibly.  The "ldmadmin" script uses the context of the particular
command to interpret the "-q" option, however.  So for "ldmadmin
mkqueue", the "-q" option specifies the regular product-queue but
for "ldmadmin mksurfqueue" it specifies the "pqsurf" output queue.

I'll grant that the point is arguable.

Regards,
Steve Emmerson

Ticket Details
===================
Ticket ID: QLM-179324
Department: Support LDM
Priority: Normal
Status: Closed