On Jan 19, 3:05 pm, "Tranz" <mcass22...@hotmail.com> wrote:
> I wrote a sciprt that spins thru pids, until it gets close to 16113.
> Then it calls another sciprt that just puts the pid to sleep for 99999.
> I am hoping this will at least prove the hypothsis that this pid is
> being killed by something.
>
> I didn't end up using truss, b/c in my other test, if a kill -9 is used
> it won't tell you the issuing pid that killed it. Only if a standard
> kill (pid) is used then it will show what pid killed it.
>
> Here is the quick script I wrote up.
>
> i=0
> until [ $i -gt 10000000 ]
> do
> echo "$!" &
> pid=$!
> wait ${pid}
> if [ ${pid} -gt 16090 ] && [ ${pid} -lt 16150 ]
> then
> x=0
> until [ $x -gt 20 ]
> do
> test_loop.ksh &
> pid2=$!
> if [ ${pid2} -eq 16113 ]
> then
> echo "PID FOUND"
> fi
> x=`expr $x + 1`
> done
> sleep 400
> fi
> i=`expr $i + 1`
> done

any luck?

..