mersenneforum.org  

Go Back   mersenneforum.org > Factoring Projects > CADO-NFS

Reply
 
Thread Tools
Old 2021-10-24, 14:20   #1
EdH
 
EdH's Avatar
 
"Ed Hall"
Dec 2009
Adirondack Mtns

23×5×101 Posts
Default Can CADO-NFS Clients be Gracefully Halted Programmatically?

Once a client is invoked, it seems to continue until it receives a 410 signal from the server. If the server is halted prior to completion, that signal is never sent.

I can interrupt las via a kill PID, but the client isn't shut down. I have not found a PID for the client (.py).

For my polyselect only work, I have the server factor a small composite after the polyselect finishes, so the clients are released, but that has to come from the same source as the polyselect operation.

I'd rather find a way to gracefully close the clients that are searching for work, but a "kill" would probably be fine. I have to issue a CTRL-c at present. And, I have to do this individually for several machines. I'd prefer to do this via a script by ssh.

All thoughts welcome. . .
EdH is offline   Reply With Quote
Reply

Thread Tools


Similar Threads
Thread Thread Starter Forum Replies Last Post
Consider forcing old clients to DC? leonardyan96 PrimeNet 8 2020-09-02 11:58
How to gracefully stop mprime under linux odin Software 1 2010-04-15 20:45
Thin Clients moo Hardware 0 2006-11-14 06:30
PRP/LLR clients OmbooHankvald Prime Sierpinski Project 11 2005-07-13 21:24
Factoring performance on different clients koekie Software 1 2003-10-16 14:35

All times are UTC. The time now is 17:22.


Thu Oct 28 17:22:28 UTC 2021 up 97 days, 11:51, 0 users, load averages: 1.53, 1.52, 1.45

Powered by vBulletin® Version 3.8.11
Copyright ©2000 - 2021, Jelsoft Enterprises Ltd.

This forum has received and complied with 0 (zero) government requests for information.

Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or any later version published by the Free Software Foundation.
A copy of the license is included in the FAQ.