Modify sources + compile.
It was just a test and it's working. DocMaboul will implement it in his BoincStudio application - in Beta only for the moment, but in distribution in a very close future -. In BoincStudio, there is also my solution to claim the good number cobblestones including optimized applications.
I strongly support increasing the 32 WU limit, here's an example.
One of my team members runs into the 32 limit at work. His company recently blocked all ports over 1000, so once a week he has been copying off his work BOINC directories, copying them to the home PC, and connecting from there to report and DL new WUs.
He is a very productive member, and IMO, a credit to both E@H and BOINC for his willingness to do this task each week.
Of course with the fabulous new akosf apps, he runs into the 32 WU limit very quickly, and the detach-reattach solution will not work for him, AFAIK.
I hesitate to suggest he diversify to more projects, because that would double the amount of "sneaker-netting" he would have to do. (Although if he is amenable to running CPDN, that might be an option.)
So I join the others here in hoping the Einstein@Home team will consider raising the limit. Thanks for listening.
His company recently blocked all ports over 1000, so once a week he has been copying off his work BOINC directories, copying them to the home PC, and connecting from there to report and DL new WUs.
I thought all boinc projects used port 80 (not counting the remote admin port, which isn't needed).
[
I thought all boinc projects used port 80 (not counting the remote admin port, which isn't needed).
Spare Cycles, thanks for the reply!
I'm checking this out with the user now. Since I use BV for monitoring, the port number 1043 just stuck in my senior-citizen's mind and got associated with everything BOINC uses.
It's possible that's what happened to him as well, if he couldn't control his work machines, he thought they had stopped talking to the servers...
Hello all, ...
I hesitate to suggest he diversify to more projects, because that would double the amount of "sneaker-netting" he would have to do. (Although if he is amenable to running CPDN, that might be an option.)
So I join the others here in hoping the Einstein@Home team will consider raising the limit. Thanks for listening.
Hello, Ken.
You could scan through some of the recent threads for one on just this subject, it has been considered, continues to be considered, in fact.
Long story short - the servers that E@H has (at this point) cannot accomodate so much increased traffic and size in the database; they will need an upgrade before the daily limit can be doubled again. Otherwise, such an obvious move would have been made almost immediately, because Akos' apps soon made E@H aware that such a doubling was needed. I personally think that the "short-handed server" situation is in large part responsible for the delay in making Akos' work "official" and downloadable from the project site, as well.
Michael R.
microcraft
"The arc of history is long, but it bends toward justice" - MLK
Thanks very much for the reply; it's good to know that the problem is only money.
And sorry for not searching first, I thought the current thread topic was close. -oops.
Ken
Ken,
I wasn't suggesting that you'd been neglectful in not looking around first. What I mean is that there may be more accurate/to the point/recent news on the topic.
Michael R.
microcraft
"The arc of history is long, but it bends toward justice" - MLK
RE: 7 hours a day without
)
You can say us, what exactly you did?
Thx.
RE: You can say us, what
)
Modify sources + compile.
It was just a test and it's working. DocMaboul will implement it in his BoincStudio application - in Beta only for the moment, but in distribution in a very close future -. In BoincStudio, there is also my solution to claim the good number cobblestones including optimized applications.
You could see that on my 4400+:
http://einsteinathome.org/host/558798
Hello all, I strongly
)
Hello all,
I strongly support increasing the 32 WU limit, here's an example.
One of my team members runs into the 32 limit at work. His company recently blocked all ports over 1000, so once a week he has been copying off his work BOINC directories, copying them to the home PC, and connecting from there to report and DL new WUs.
He is a very productive member, and IMO, a credit to both E@H and BOINC for his willingness to do this task each week.
Of course with the fabulous new akosf apps, he runs into the 32 WU limit very quickly, and the detach-reattach solution will not work for him, AFAIK.
I hesitate to suggest he diversify to more projects, because that would double the amount of "sneaker-netting" he would have to do. (Although if he is amenable to running CPDN, that might be an option.)
So I join the others here in hoping the Einstein@Home team will consider raising the limit. Thanks for listening.
Ken
RE: His company recently
)
I thought all boinc projects used port 80 (not counting the remote admin port, which isn't needed).
http://boinc-wiki.ath.cx/index.php?title=Protocol_Overview
"All communication uses HTTP on port 80, so the BOINC Client Software can function through Firewalls and Proxies."
RE: [ I thought all boinc
)
Spare Cycles, thanks for the reply!
I'm checking this out with the user now. Since I use BV for monitoring, the port number 1043 just stuck in my senior-citizen's mind and got associated with everything BOINC uses.
It's possible that's what happened to him as well, if he couldn't control his work machines, he thought they had stopped talking to the servers...
Thanks again very much for your post...
Ken
RE: Hello all, ... I
)
Hello, Ken.
You could scan through some of the recent threads for one on just this subject, it has been considered, continues to be considered, in fact.
Long story short - the servers that E@H has (at this point) cannot accomodate so much increased traffic and size in the database; they will need an upgrade before the daily limit can be doubled again. Otherwise, such an obvious move would have been made almost immediately, because Akos' apps soon made E@H aware that such a doubling was needed. I personally think that the "short-handed server" situation is in large part responsible for the delay in making Akos' work "official" and downloadable from the project site, as well.
Michael R.
microcraft
"The arc of history is long, but it bends toward justice" - MLK
Michael, Thanks very much
)
Michael,
Thanks very much for the reply; it's good to know that the problem is only money.
And sorry for not searching first, I thought the current thread topic was close. -oops.
Ken
Ken
RE: Michael, Thanks very
)
Ken,
I wasn't suggesting that you'd been neglectful in not looking around first. What I mean is that there may be more accurate/to the point/recent news on the topic.
Michael R.
microcraft
"The arc of history is long, but it bends toward justice" - MLK