Pause, Suspend, and Resume

[GoogleCodeExporter]

Currently, you can set a limit on the number of URLs to reconstruct by using 
the -n X switch, and you can later resume the job to get another batch (of the 
same size), by using the -R PID_computername.save switch.

It would be convenient if a job that didn't have a limit set could also be 
stopped and then resumed where it left off.

Potential solutions:

1. When the job is stopped by using ctrl-C, a PID_computername.save is written 
out which can later be used to resume the job.

2. When the job is stopped by using another key combination (such as Q for quit 
or S for Suspend), a PID_computername.save is written out which can later be 
used to resume the job.

3. Jobs can be paused by using P, and resumed by using R, without ending the 
process.

Original issue reported on code.google.com by mich...@urbsly.com on 27 Apr 2012 at 2:46

[GoogleCodeExporter]

Not that this isn't a valid concern, but there exist machine- and OS-level 
commands for each of these functions, and to override them would be the "wrong" 
thing to do. For example, the suspend and cancel commands are for specific 
purposes (ctrl+Z, eg.). If we override these features, we may be preventing a 
runaway process from being shut down from the terminal.

Original comment by jbrunell...@gmail.com on 10 May 2012 at 12:16

• Changed state: WontFix