Discussion related to cado-nfs

[Emmanuel Thomé <Emmanuel.Thome@inria.fr>]

Hi,

On Tue, Feb 01, 2022 at 03:20:43AM +0000, Ed Hall wrote:
> Hello Team,
>
> It there a manner to have CADO-NFS issue a 410, closing the clients
> when tasks.sieve.run=false?  If not, could a method be added?  When
> performing polyselect only, for larger jobs (as well as other
> taskings), the clients keep pinging the server machine after the server
> has exited.  My work around for an automated setup with many external
> clients, has been to run a smaller complete job after the polyselect
> has finished.  This is not ideal. Thanks.

Yes, this is a good suggestion.

Implementation is trickier than it seems.  We're touching on some of the
brittle aspects of the cado-nfs server, here. The server would have to
wait for the clients to ask for work so that it gets a chance to answer
410. Presumably, waiting for (what the server think is) the clients sleep
time could be appropriate.

I may have a try at this, but that won't be immediate.

Best regards,

E.

> 
> Sincerely,Ed Hall