Feature #27

Maximal no-progress-threshold should be configurable

Added by jbk over 7 years ago. Updated about 7 years ago.

Status:ClosedStart date:04/05/2010
Priority:LowDue date:
Assignee:jbk% Done:

100%

Category:ClientEstimated time:5.00 hours
Target version:v0.3s - Sunflower

Description

Sometimes the built-in threshold in the client of 2 hours of no progress is simply too little. The threshold hould be configurable and sent with the workunit.

History

#1 Updated by jbk over 7 years ago

  • Target version set to v0.3s - Sunflower

#2 Updated by jbk about 7 years ago

Suggested commandline arguments:
[-k|--kill x] Where x is the number of seconds that the unit should be allowed to run with no progress before being killed. Default is 3600*2

#3 Updated by jbk about 7 years ago

  • Status changed from New to Resolved
  • % Done changed from 0 to 100

Applied in changeset r1201.

#4 Updated by jbk about 7 years ago

  • Status changed from Resolved to Closed
  • Assignee set to jbk

Also available in: Atom PDF