Mark_Conty AT cargill DOT com wrote:

The fact that it's doing a 'tar -tf -', though, in conjunction with the errors from amstatus when I finally killed it, indicated that it was still in the estimate stage:

FAILURE AND STRANGE DUMP SUMMARY:
  s3sme      /var/opt/ignite/recovery RESULTS MISSING
  s3sme      /var/opt/patch/master_11X_patches/PHSS_^2 RESULTS MISSING

s3sme /var/opt/patch/master_11X_patches/PHSS_25-29 RESULTS MISSING

  s3sme      /var/opt/patch/master_10X_patches/PHSS RESULTS MISSING

So it hadn't even _gotten_ to the point of dumping these DLEs. *sigh* But still, the 10,800-second etimeout was supposed to have been in effect, and it had long lapsed.

That is 10800 seconds for each DLE on that host.  If you have 5 DLE's
on that host, the timeout would become effective after 5*10800 seconds.

How many DLE's do have for that host?

if you specify a negative number, than that will be taken as the total
time for the total estimate phase, no matter how many DLE's.

Does anyone have any idea why _this_ timeout didn't take effect, either?

--
Paul @ Home