Quote from: rico666 on November 10, 2016, 06:55:34 AM

Quote from: Jude Austin on November 10, 2016, 12:43:13 AM

Technicalities! I was pressing 'e' and after the chunk it was working on it downloaded a new chunk and kept going.

I know about that. You basically pressed 'e' when the current chunk was about to end (in the last loop iteration).
The the command gets interpreted at the start of the next iteration (which it ends gracefully).

On my notebook, with -c 4 -t 10 it looks like this. "c 4" means that there are 'oooo' chunks, so

Code:

Ask for work... got blocks [131193289-131194632] (1409 Mkeys) v latest possible time to 'e' for current round, else ending at the end of next round
oooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooo oooooooo
Ask for work... got blocks [131209977-131211320] (1409 Mkeys)

vvvvvvv if you Ctrl+C on the beginning, there will be a promised but undelivered block, but not much work lost
oooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooo
the later you press Ctrl+C after a new round has been started, ^^^^^^
the more work (of your computer) you lose/waste. |
really bad time to press Ctrl+C

Ask for work... got blocks [131226665-131228008] (1409 Mkeys)
ooooooooooooooooooooooooooooooooooooooooooe
o
END requested. (Ending this loop) Waiting for children to finish...
ooooooooooooooooooooooooooooooooooooooooo

It looks like unnecessary much science, but the upside for this is, it takes 0 (in words: zero) CPU time to process.

Rico

Last night I pressed 'e' and then enter and I just logged in and the screen session was dead, so it worked.

I was probably just impatient and using a large time of work.

Thanks again!

Jude