T
Tim Hutchens
Guest
James - I was aware of ProTop, but it had fallen off my radar. I'll take another look at it. Tom - I looked closer at the difference between the procore and protrace files. procore is written to the current directory by default, or to the temporary directory if the -T parameter is specified. protrace is written in the current directory and does not appear to be affected by the -T parameter. If I understand this correctly, the procore file may still end up with a filesize of 0 in the -T directory, but the protrace would not be affected by the full filesystem and would be created successfully (assuming -T is actually in a different filesystem). Does this sound correct? That would certainly help if we could get the ABL stack trace of the offending session. Is the -t parameter required to make the protrace file visible? I have seen protrace files on our system before, so I'm assuming not. Also, the -t parameter documentation mentions that you will need to manually delete the temp files from aborted sessions if the parameter is set. I'm hesitant to set this flag with our ongoing problem, because the problem currently "resolves" itself by removing the temp file when the session aborts. Setting the -t parameter may cause the problem to last longer than it currently does because of the required manual file removal. Of course, if it helps us solve the root cause, it's probably worth it. Thank you, Tim
Continue reading...
Continue reading...