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

Re: strange pqact behavior.



Eric,

>Date: Mon, 22 Aug 2005 16:28:42 -0500 (CDT)
>From: Eric Nelson <address@hidden>
>To: Steve Emmerson <address@hidden>
>Subject: Re: strange pqact behavior. 

The above message contained the following:

> Here are the results... (sorry for the line wrapping)
> 
> climate:~> ps -ef | awk 'NR==1 || /pqact/'
> ldm  26177 26175  0 16:19 ? 00:00:00 pqact -f ANY 
> /home/ldm/etc/pqact.split.wxp
> ldm  26178 26175  3 16:19 ? 00:00:03 pqact -f ANY 
> /home/ldm/etc/pqact.split.dave
> ldm  26179 26175  0 16:19 ? 00:00:00 pqact -f ANY 
> /home/ldm/etc/pqact.split.mcidas
> ldm  26180 26175  6 16:19 ? 00:00:05 pqact -f ANY 
> /home/ldm/etc/pqact.split.gempak
> ldm  27152 26177  0 16:20 ? 00:00:00 pqact -f ANY 
> /home/ldm/etc/pqact.split.wxp
> ldm  27267 26177  0 16:20 ? 00:00:00 pqact -f ANY 
> /home/ldm/etc/pqact.split.wxp
> ldm  27268 26177  0 16:20 ? 00:00:00 pqact -f ANY 
> /home/ldm/etc/pqact.split.wxp
> ldm  27269 26177  0 16:20 ? 00:00:00 pqact -f ANY 
> /home/ldm/etc/pqact.split.wxp
> ldm  27270 26177  0 16:20 ? 00:00:00 pqact -f ANY 
> /home/ldm/etc/pqact.split.wxp
> ldm  27274 21835  0 16:20 pts/0    00:00:00 awk NR==1 || /pqact/
> ldm  27295 26177  0 16:20 ? 00:00:00 pqact -f ANY 
> /home/ldm/etc/pqact.split.wxp
> ldm  27296 26177  0 16:20 ? 00:00:00 pqact -f ANY 
> /home/ldm/etc/pqact.split.wxp
> ldm  27297 26177  0 16:20 ? 00:00:00 pqact -f ANY 
> /home/ldm/etc/pqact.split.wxp
> ldm  27298 26177  0 16:20 ? 00:00:00 pqact -f ANY 
> /home/ldm/etc/pqact.split.wxp
> ldm  27299 26177  0 16:20 ? 00:00:00 pqact -f ANY 
> /home/ldm/etc/pqact.split.wxp
> ldm  27300 26177  0 16:20 ? 00:00:00 pqact -f ANY 
> /home/ldm/etc/pqact.split.wxp

The above shows two, distinct, LDM process groups: 26175, and 26177.
The closeness of those numbers indicate that they were created almost
simultaneously.

The ldmadmin(1) script should create only one process group.

I suspect that you have something funning going on when you execute the
command "ldmadmin start".  Can you investigate?

Regards,
Steve Emmerson