How can one prevent assignment of new work?
 

Well, the title pretty much says it all. I would like to prevent the assignment of any new work on my clients so that my machines can complete all remaining work in their queue and then stop completely until I choose to turn them back on.
Is this somehow possible via a setting on the PrimeNet website or the prime95 client's configuration files?
Thanks in advance for any help. :)

I think this might work:

Go to Options --> Preferences... and set "Days of work to queue up" to 0. This should keep your client from requesting new work from PrimeNet, so it will allow you to complete your existing assignments without taking anything new.

[QUOTE=Jaxon;295797]I think this might work:

Go to Options --> Preferences... and set "Days of work to queue up" to 0. This should keep your client from requesting new work from PrimeNet, so it will allow you to complete your existing assignments without taking anything new.[/QUOTE]
Alright, just did that. I'll know in two days if it worked (that's when two of the workers will complete), but I'm having my doubts, since it was set to 5 and workers previously took 34 days on average for LL or LL-D which means new work would only be added to the queue 5 days before a worker completes and setting it to 0 would logically add new work to the queue as soon as the previous work completed and the result has been submitted to PrimeNet.

In Prime95, choose Advanced > Quit GIMPS > Yes (complete current work before quitting).

[QUOTE=Mini-Geek;295801]In Prime95, choose Advanced > Quit GIMPS > Yes (complete current work before quitting).[/QUOTE]
I don't want to quit GIMPS, I just want to turn the client off for a prolonged period of time, but complete pending work so it doesn't expire and I haven't wasted CPU time on partially solving a work unit.

I don't have access to the computer now to verify, but I think that's how I set up one of my machines to do P-1 assignments for GPU72. I was running into problems with getting PrimeNet Assignments after the GPU72 work ran out, and I think that setting the days of work to queue to 0 kept the workers idle until I was able to get around to to manually adding more assignments to worktodo.txt.

[QUOTE=Dorian;295803]I don't want to quit GIMPS, I just want to turn the client off for a prolonged period of time, but complete pending work so it doesn't expire and I haven't wasted CPU time on partially solving a work unit.[/QUOTE]

From the readme.txt file:

[code]The Quit GIMPS menu choice is used when you no longer want this
computer to work on the GIMPS project. You may rejoin at a later date.
If you are a PrimeNet user your unfinished work will be returned to the
server. If you are a manual user, you need to send me email containing
your results.txt file.[/code]
This may be a bit out of date, since it does not cover the Yes (complete current work) that mini-geek listed above.

a sarcastic reply to the title
 

maybe don't do any in the first place ?

[QUOTE=bcp19;295810]From the readme.txt file:

[code]The Quit GIMPS menu choice is used when you no longer want this
computer to work on the GIMPS project. You may rejoin at a later date.
If you are a PrimeNet user your unfinished work will be returned to the
server. If you are a manual user, you need to send me email containing
your results.txt file.[/code]
This may be a bit out of date, since it does not cover the Yes (complete current work) that mini-geek listed above.[/QUOTE]

This is correct; quitting GIMPS does not erase your records in the database, all it really does is stop queuing more work. If DaysOfWork=0 does not work, then do the quit GIMPS thing, which isn't permanent at all. You can keep Prime95 exactly as it is and restart it at any time, and your username/account/computer will be exactly as they were on PrimeNet.
(Edit: It is a bit out of date, but it is essentially correct, and marking the checkbox that Mini-Geek described will allow you to finish your work before stopping.)

NoMoreWork=1

[QUOTE=Xyzzy;295820]NoMoreWork=1[/QUOTE]:goodposting:I remembered that there was a setting like that, but was too lazy at the time to look it up.

[QUOTE=Xyzzy;295820]NoMoreWork=1[/QUOTE]
This is what the Quit GIMPS option does behind-the-scenes when you choose Yes. If you prefer, you can set it with that option in prime.txt instead.

[QUOTE=Jaxon;295807]I don't have access to the computer now to verify, but I think that's how I set up one of my machines to do P-1 assignments for GPU72. I was running into problems with getting PrimeNet Assignments after the GPU72 work ran out, and I think that setting the days of work to queue to 0 kept the workers idle until I was able to get around to to manually adding more assignments to worktodo.txt.[/QUOTE]
Well, I can confirm that this method does not work with the official prime95, prime95 (x86_64) and WindowsService clients.
[QUOTE=Xyzzy;295820]NoMoreWork=1[/QUOTE]
This is exactly what I was looking for. Let's hope it works.

[QUOTE=Jaxon;295807]< snip > setting the days of work to queue to 0 kept the workers idle < snip >[/QUOTE]
[QUOTE=Dubslow;295818]< snip > If DaysOfWork=0 does not work, < snip >[/QUOTE]AFAIK DaysOfWork='s purpose is to specify a [I]minimum[/I] (not maximum) number of days' work to queue up. (So, "MinimumDaysOfWork=" might've been less confusing.) Therefore, it never prevents new assignments.

Setting DaysOfWork=0 says that the user is not requesting more than one assignment (regardless of how short its estimated time to completion) at a time, not that the user wants no assignment at all. IIUC the result would be that PrimeNet sends one new assignment if the queue is empty, but no new assignment if there remains at least one uncompleted assignment.

(Note that [I]queue[/I] refers to an individual worker thread's queue, so the user specifying DaysOfWork=0 would still have at least as many assignments as worker threads.)