Maybe my concern is misplaced, but it bothers me that during the whole outage my computer is sending useless requests to u/l my completed WUs. I tried Suspending the project, but since there were results already present, all that did is prevent more requests for d/l WUs.

I would have posted this in Outage Observations/Comments except I have no suggestions here, only a question. I didn't want to muddy that thread.

---

switch to other projects, just share the computers.... i have only one computer running seti wu at this point in time along with other projects so that computer isn't dependent upon one project and idle on Tuesdays. all others are running a mix of projects...

---

I recommend Secunia PSI: http://secunia.com/vulnerability_scanning/personal/
Go Georgia Tech.

Maybe my concern is misplaced, but it bothers me that during the whole outage my computer is sending useless requests to u/l my completed WUs. I tried Suspending the project, but since there were results already present, all that did is prevent more requests for d/l WUs.

I would have posted this in Outage Observations/Comments except I have no suggestions here, only a question. I didn't want to muddy that thread.

I have had similar thoughts. After some thinking and discussion, I realize that these extra requests only have an impact on your computer, and not on the project as a whole. If you notice your computer slowing down or having problems with Internet speeds, go to the "Activity" tab in BONIC Manager, and select "Network activity suspended" until the outage is over. Unfortunately, this affects any other BOINC projects as well.

If your computer is working fine, just shrug your shoulders, say "oh well" and carry on.

---

Maybe my concern is misplaced, but it bothers me that during the whole outage my computer is sending useless requests to u/l my completed WUs. I tried Suspending the project, but since there were results already present, all that did is prevent more requests for d/l WUs.

I would have posted this in Outage Observations/Comments except I have no suggestions here, only a question. I didn't want to muddy that thread.

There was a thread a few days ago on how to set the prefs so the computer wont connect during the outage.
Here is the thread : http://setiathome.berkeley.edu/forum_thread.php?id=60742

---

Maybe my concern is misplaced, but it bothers me that during the whole outage my computer is sending useless requests to u/l my completed WUs. I tried Suspending the project, but since there were results already present, all that did is prevent more requests for d/l WUs.

I would have posted this in Outage Observations/Comments except I have no suggestions here, only a question. I didn't want to muddy that thread.

Just suggestion/comment thinking. One possible solution to this could be to ask BIONC on their next/future release to add some sort of network suspenion routine to the suspend project routine button.

Michael

Just suggestion/comment thinking. One possible solution to this could be to ask BIONC on their next/future release to add some sort of network suspenion routine to the suspend project routine button.

Michael

This is already there in current release of BOINC, under the "Activity" tab.

---

Just suggestion/comment thinking. One possible solution to this could be to ask BIONC on their next/future release to add some sort of network suspenion routine to the suspend project routine button.

Michael

This is already there in current release of BOINC, under the "Activity" tab.

The trouble with that is that it cuts off network access for other projects too. There was a proposal, and code written, for a project-by-project network suspension button, but David Andseron refused to accept it: [trac]#139[/trac].

Assuming that the three-day outages are a medium-to-long term plan for SETI, and the BOINC philosophy would be for people to have network access to other projects during that time, maybe the time has come to push again on that front: fresh input would possibly help.

But please be careful to phrase it as a useful BOINC enhancement, not a SETI moan. We've lost that ticket once already, don't want another premature closure.

Point taken Richard as DA has rejected a (project-by-project network suspension button). I will not press it any further.

Michael

Point taken Richard as DA has rejected a (project-by-project network suspension button). I will not press it any further.

Michael

I don't think Richard was saying this is a bad idea and shouldn't be revisited, just that it should be handled tactfully.

Point taken Richard as DA has rejected a (project-by-project network suspension button). I will not press it any further.

Michael

I don't think Richard was saying this is a bad idea and shouldn't be revisited, just that it should be handled tactfully.

Correct!

Point taken Richard as DA has rejected a (project-by-project network suspension button). I will not press it any further.

Michael

I don't think Richard was saying this is a bad idea and shouldn't be revisited, just that it should be handled tactfully.

Correct!

I also agree with Richards second statement ( maybe the time has come to push again on that front: fresh input would possibly help.)

Haveing worked for NORTEL getting software designers to change something they have rejected does take a lot of tact and knowledge of the system involved.

Haveing read the post again I can not find anything that suggest he did say or intermate it to be a bad idea.

Also uderstood his last statement (But please be careful to phrase it as a useful BOINC enhancement, not a SETI moan)

Just goes to show how easy it is to write something and then read it out of context.

Michael

I already have another project, Rosetta. Since the Rosetta WUs generally take 18 to 30 hours to process, I guess I could turn off network communications for the duration of the outage. The BOINC local preferences seem to have a negative reversal of anti-meaning, which makes them hard to understand.

I suppose if I have 4 days of Rosetta, I can do without communicating with either project for a while, but it's not my first choice. I think what I'll try to do is turn off network communication with the local preferences for 1 day (maybe Wednesday) and see how that goes.

What I'd like is to be able to override my network preference with a manual Update from BOINC. I'll see if that works.

---

What I'd like is to be able to override my network preference with a manual Update from BOINC. I'll see if that works.

If you are going to be doing manual updates anyway, leave network activity off during the outage, except while you do the manual updates.

---

I already have another project, Rosetta. Since the Rosetta WUs generally take 18 to 30 hours to process, I guess I could turn off network communications for the duration of the outage. The BOINC local preferences seem to have a negative reversal of anti-meaning, which makes them hard to understand.

I suppose if I have 4 days of Rosetta, I can do without communicating with either project for a while, but it's not my first choice. I think what I'll try to do is turn off network communication with the local preferences for 1 day (maybe Wednesday) and see how that goes.

What I'd like is to be able to override my network preference with a manual Update from BOINC. I'll see if that works.

You might want to check out the thread Prefs: Day-of-week override.

---

SETI@home classic workunits: 93,865 CPU time: 863,447 hours
Join the [url=http://tinyurl.com/8y46zvu]BP6/VP6 User Group[