Does anyone know how (if possible) to prevent work units from being sent to you? I have a couple of crunchers I need to stop for a while and don't want to download anything I won't be able to return. Would changing the days to connect to network to zero work?

---

> Does anyone know how (if possible) to prevent work units from being sent to
> you? I have a couple of crunchers I need to stop for a while and don't want
> to download anything I won't be able to return. Would changing the days to
> connect to network to zero work?
>

Yep.
If you create a separate profile (work or school) and move them there, you can keep
your other hosts busy.

Regards Hans

---

I already have separate profiles, but right now they aren't updating correctly. Just wondering if it will work before I do something stupid.

---

I wouldn't worry too much about loosing a few wu's. They will get recycled.

---

Paul
(S@H1 8888)
And proud of it!

Unless they are CPDN WUs. I really do wish there was a way to set the client to finish and upload any current WUs but do not download any new work.

Jim

> I wouldn't worry too much about loosing a few wu's. They will get recycled.
>

---

> I really do wish there was a way to set the client
> to finish and upload any current WUs but do not download any new work.
>
> Jim
>
Yes, there's plenty of scenarios where one would want to finish crunching the WU's in the cache (or as many as possible) without downloading new one's. A simple "no download" under the file menu would seem to be quite easy to implement.

---

<img src='http://www.boincsynergy.com/images/stats/comb-912.jpg'>

A simple way of preventing new WU is this:

Got to the preference for the particular venue (home/work/school) and set the "leave atleast X diskspace" to a number larger than you have (like 30 gb for a 10 gb drive).

(update preferences on your client)

That way, when a new download is attempted, the scheduler will will respond with something like "there was work but you don't have enough disk space".

Current work will complete, but no new work will download


Note - this will impact all computers in the same venue!

---

> Unless they are CPDN WUs. I really do wish there was a way to set the client
> to finish and upload any current WUs but do not download any new work.
>
> Jim
>
> > I wouldn't worry too much about loosing a few wu's. They will get
> recycled.

This feature has been added to latest source code, not sure if there's a compiled client with it yet.

I don't know what David called the menu option, I refer to it as Phaseout (as in phasing out of the project).

There is already a thread explaining how to change venues just look here

Just set your connect to network every x days to 0.1 and your 'Leave at least' to very high so BOINC has no space left to d/l more work and old work is reported. You should also set this pc in his own venue.

---

BOINC Doc | Team-Site | BOINC-Podcast

> A simple way of preventing new WU is this:
>
> Got to the preference for the particular venue (home/work/school) and set the
> "leave atleast X diskspace" to a number larger than you have (like 30 gb for a
> 10 gb drive).
>
> (update preferences on your client)
>
> That way, when a new download is attempted, the scheduler will will respond
> with something like "there was work but you don't have enough disk space".
>
> Current work will complete, but no new work will download
>
>
> Note - this will impact all computers in the same venue!
>

Thanks for that tip, azwoody!
I intend upgrading from this pile of junk I'm using at the moment and I was wondering how to do it without having workunits go 'into limbo'!
My plan now is to use your tip to complete all WUs, then exit & un-install BOINC from this PC.
On the new PC (correct me if I'm wrong) I just download new BOINC and use the key etc. which I still have.

I'll be glad to see the back of this machine - 128MB RAM Celeron 2.4GHz; completes WUs in 10hrs+ .......

---

There is also another alternative explained here, putting the avalaible space at 0.0001GB.

When putting the preferences in this way, you get following:
SETI@home - 2005-01-13 14:20:30 - Requesting 810364 seconds of work
SETI@home - 2005-01-13 14:20:30 - Sending request to scheduler: http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
SETI@home - 2005-01-13 14:20:33 - Scheduler RPC to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi succeeded
SETI@home - 2005-01-13 14:20:33 - Message from server: No work available (there was work but you don't have enough disk space allocated)
SETI@home - 2005-01-13 14:20:33 - No work from project

Thanks folks, I added those tricks to the new DB-driven FAQ ...

---

@ John Hunt

> I'll be glad to see the back of this machine - 128MB RAM Celeron 2.4GHz;
> completes WUs in 10hrs+ .......
>

there are plenty of us (me included) that would be happy to take that machine if you are wanting to donate :)
i'll even pay shipping costs *smiles*

---

S@h Berkeley's Staff Friends Club

Damn, I'd even pay for the machine itself...

---

<img src="http://www.boincstats.com/stats/banner.php?cpid=d2319b8f0ad14565556d0ba45b64e779">

Actually, just disable the network until all units are crunched, set your putting the available space at near zero (0.0001GB) then re-enable it once the WUs are done.

---

Stewie: So, is there any tread left on the tires? Or at this point would it be like throwing a hot dog down a hallway?

Fox Sunday (US) at 9PM ET/PT