Thanks for the detailed response. I was worried that this was going to turn into a subtle and problematic situation per your response. I will study what you have written on exec, but it does sound like the whole thing is a little touchy
Basically the reason I was hoping for correlation between the forkManger & top cmd PIDs is as follows. Lets say I submit 3 jobs(call them j1,j2,j3) using my forkManager code. During the submission process my code prints to stnd out log info related to the submission flow. ie j1:PID=123, j2:PID=130, j3:PID=140, etc. It also keeps track of when the jobs complete via the forkManager. These jobs dont all run at the same rate, some run for hrs or even days. At some point while the jobs are still running I may decide that the j2 is no longer needed. So I would like to go into my log and find the PID for the the thing I symbolically know an love as j2. I would like to be able to use that logged PID to issue a kill on said PID. The problem is that the PID as reported in 'top' are not what is stored in the log. Hence the log PIDs can't be used to issue the kill cmd.
Frankly correlation is not an absolute requirement. But never the less, it would have been nice. So unless someone comes up with an easy, bullet proof fix for this. I most likly wont be killing myself to make it happen. I'm not sure I am versed enough to work around all the potential land mines to which you eluded.
In reply to Re^5: forkManager PID 1 less than top
by MAR99
in thread forkManager PID 1 less than top
by MAR99
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |