Add a way for the cado-nfs clients to stop when the server was prematurely stopped on purpose
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.