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

Re: strange pqact behavior.

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: Re: strange pqact behavior.
  • Date: Tue, 23 Aug 2005 08:36:15 -0600
Eric,

The following ps(1) lines in your previous email

UID        PID  PPID  C STIME TTY          TIME CMD
ldm      11254 11252  0 16:36 ?        00:00:00 pqact -f ANY 
/home/ldm/etc/pqact.split.wxp
ldm      11257 11252  2 16:36 ?        00:00:04 pqact -f ANY 
/home/ldm/etc/pqact.split.gempak
ldm      13889 11257  0 16:39 ?        00:00:00 pqact -f ANY 
/home/ldm/etc/pqact.split.gempak
ldm      13943 11254  0 16:39 ?        00:00:00 pqact -f ANY 
/home/ldm/etc/pqact.split.wxp
ldm      13944 11254  0 16:39 ?        00:00:00 pqact -f ANY 
/home/ldm/etc/pqact.split.wxp

Show that pqact(1) process 13889 was started by pqact(1) process 11257
and that pqact(1) processes 13943 and 13944 were started by pqact(1)
process 11254.  The pqact(1) configuration-files "pqact.split.gempak" and
"pqact.split.wxp" must contain (directly or indirectly) instructions to 
execute the pqact(1) program.

Because this is causing problems, I suggest you look over those
configuration-files to discover the cause.

Regards,
Steve Emmerson