[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.)