Quote from: rico666 on November 08, 2016, 10:26:26 PM

Quote from: bobsmoke on November 08, 2016, 08:52:54 PM

I think I understood it. So, it seems that you can fetch work but then if you stop the execution of the program that work will be lost. is that it?

Yes.

Quote

What will be the best way to stop LBC in a graceful manner?

It's somewhat hidden in the README.txt, I will put it in the User Manual on the web pages:

Quote

You press 'e', after a while the message

END requested. (Ending this loop) Waiting for children to finish...

will appear. The LBC client will not stop immediately, but finish the
blocks in the current loop. Contrary to immediate quitting, this has
the advantage that proof of your work done is submitted to the server
and your work is not "lost".

Quote

.. and if there is no way to stop it gracefully you can just stop it and then process the blocks interval you were working with --pages -, right?

If you do not stop it gracefully, the blocks will be re-issued after some time. The problem here was, that you issued the query command before your client had delivered ANY block and so the client was not yet known in the clients DB. Of course under such circumstances a query caused some stir. It's fixed now.

Rico

Just wanted to chime in, when I press E to end gracefully it doesn't terminate after the loop.

Unless of course it has to do it for each thread, I most likely got impatient and terminated it ungracefully.

Thanks,
Jude