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

20030731: Questions/issues with pqact

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: 20030731: Questions/issues with pqact
  • Date: Thu, 31 Jul 2003 12:55:55 -0600
Steven,

>Date: Thu, 31 Jul 2003 12:34:55 -0500
>From: Steven Danz <address@hidden>
>Organization: Aviation Weather Center
>To: Steve Emmerson <address@hidden>
>Subject: Re: 20030731: Questions/issues with pqact

The above message contained the following:

> Right, but say pqact closes its end of the pipe, and the decoder is
> 'busy', could be swapped out, could be writing/creating a file, etc.
> and hasn't recognized that the EOF has been sent.  I'm wondering if it
> is possible that pqact is off starting anew decoder since it closed
> its end of the pipe while the previous decoder hasn't actually exited
> yet.

As far as I know, that's entirely possible.  One of my colleagues (Tom
Yoksas) has said that he's seen this behavior on systems that are being
pushed to their limits.  His solution was to use multiple pqact(1)s.

Regards,
Steve Emmerson