2665825693
Wouldn't be so bad, except...the errmgr orders the termination of ALL procs, which kills any other job that should have been left alone. Add a new proc and job state indicating "killed_by_cmd" so we can tell the difference between a proc/job that was deliberately terminated by us vs one that is killed by external signal. This change was tested to ensure it didn't interfere with ctrl-c operation (it doesn't - we order termination of all jobs when we get a ctrl-c). This commit was SVN r22100.