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

[LDM #HRO-913624]: LDM idea for slow pipes

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 #HRO-913624]: LDM idea for slow pipes
  • Date: Tue, 16 Jan 2007 09:12:30 -0700
Daryl,

> I have a low priority RFE for ya.  I've been working to diagnose some slow
> decoders I have written and so I see messages in my ldmd.log file like so:
> 
> Jan 13 16:55:44 mesonet pqact[10044] WARN: write(11,,4096) to pipe took
> 5.446503 s
> 
> It would be really nice if that message could actually tell me which
> decoder is slow.  I believe you recently added support so that when the
> decoder dies, a message like this is printed.
> 
> Jan 12 09:59:54 mesonet pqact[10046] ERROR: pbuf_flush (9) Timed out
> Jan 12 09:59:54 mesonet pqact[10046] ERROR: pipe_put: scripts/metarObFe.py
> write error
> 
> So it would be nice to have a message like this:
> 
> Jan 13 16:55:44 mesonet pqact[10044] WARN: write(11,,4096)
> to scripts/metarObFe.py [$pid] took 5.446503 s

Good idea.  I'll see what I can do.


Regards,
Steve Emmerson

Ticket Details
===================
Ticket ID: HRO-913624
Department: Support LDM
Priority: Normal
Status: Closed