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

Re: strange pqact behavior.



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


NOTE: All email exchanges with Unidata User Support are recorded in the Unidata inquiry tracking system and then made publicly available through the web. If you do not want to have your interactions made available in this way, you must let us know in each email you send to us.