If someone knows, how to optimise
6.x to use only information in an arbitrary subdirectory, this would be an
option for me to update BOINC from 5.10 to 6.x
There are two command-line options of the client that might help:
* "--insecure" should switch off the "sandboxing" (requiring a "boinc" user account)
* "--dir /var/tmp/BOINC" allows to put the BOINC data directory anywhere you like, in the example to /var/tmp/BOINC, which should be local on all machines on a cluster (as an Admin I'd prefer /var/lib/boinc)
BM
Fortunately --insecure works ;o)
I managed to update BOINC on all related computers before Xmas ...
So I trust this user will be told how to upgrade, since I don't know what the hell you're talking about. Such mysterious and clandestine motives. For most of us, we're just running your Boinc software. We don't know what the hell you're talking about. Talk to the majority of your users, not the geek specialists. Most of us are out here just trying to help out. Get a grip and give the illiterate Boinc crowd some slack.
From one non-geek specialist to another:
An upgrade is generally no problem, particular if one is running the windows BOINC version, as you appear to be (5.4.9).
I'd suggest running your computer out of work first, just in case something untoward happens. Tap the activity tab in the BOINC manager, and set network activity to "suspended" and then let BOINC finish out the work it has.
After that happens, download the newest windows client from here (6.10.58). Install it and it will copy over and replace the BOINC stuff of your old client. After that, set the activity back to "network activity based on preferences" or "network activity always available" if not already so and your done.
...Tap the activity tab in the BOINC manager, and set network activity to "suspended" and then let BOINC finish out the work it has...
I would not suspend network activity, because then the finished tasks aren't uploaded. Instead, select each of your active projects in the Projects tab and click "No new tasks" in turn.
After all tasks have been uploaded, click the Update button for each project in turn to report them.
When your Tasks tab is totally empty, proceed as Erik suggested.
If you don't want to upgrade to BOINC rev 6, you can also upgrade to 5.8.16 (a version still without separate data directory). To get it, click the All versions link in the window Erik linked to.
Gruß,
Gundolf
Computer sind nicht alles im Leben. (Kleiner Scherz)
Does anyone ever had a task failing just because of a Core Client update? I vaguely remember such things from the 4.x series and occasionally development versions, but have not seen anything like that with recommended versions since back then.
I usually just download & install a new Core Client even if the old one is still running. Only on Linux I bother terminating the older one first, on Windows & Mac I leave that to the installer.
Maybe I'm a bit too lazy, but I don't care much even if I get one or two failing tasks.
...Tap the activity tab in the BOINC manager, and set network activity to "suspended" and then let BOINC finish out the work it has...
I would not suspend network activity, because then the finished tasks aren't uploaded.
Ah, you are correct Gundolf Jahn. My apologies if I led anyone wrong, I just recent (late last month) got back into BOINC/Einstein and time has me befuddled apparently.
Does anyone ever had a task failing just because of a Core Client update? I vaguely remember such things from the 4.x series and occasionally development versions, but have not seen anything like that with recommended versions since back then.
I usually just download & install a new Core Client even if the old one is still running. Only on Linux I bother terminating the older one first, on Windows & Mac I leave that to the installer.
Maybe I'm a bit too lazy, but I don't care much even if I get one or two failing tasks.
BM
After giving it some more thought with your post in mind, I believe you are correct. I realize now that I was thinking of losing tasks when forcing application changes (a la Akos Fekete back in the day).
So much fail today.... I'll go put my nose into a corner now.
fyi : The reason why I used 4.19 on one box so long has been trouble with the proxy authentication. 4.19 had Berkeley code for that, later versions used the curl library. Not much lost, it's just an old and inefficient P4.
RE: RE: If someone knows,
)
Fortunately --insecure works ;o)
I managed to update BOINC on all related computers before Xmas ...
RE: So I trust this user
)
From one non-geek specialist to another:
An upgrade is generally no problem, particular if one is running the windows BOINC version, as you appear to be (5.4.9).
I'd suggest running your computer out of work first, just in case something untoward happens. Tap the activity tab in the BOINC manager, and set network activity to "suspended" and then let BOINC finish out the work it has.
After that happens, download the newest windows client from here (6.10.58). Install it and it will copy over and replace the BOINC stuff of your old client. After that, set the activity back to "network activity based on preferences" or "network activity always available" if not already so and your done.
Good luck! :)
RE: ...Tap the activity tab
)
I would not suspend network activity, because then the finished tasks aren't uploaded. Instead, select each of your active projects in the Projects tab and click "No new tasks" in turn.
After all tasks have been uploaded, click the Update button for each project in turn to report them.
When your Tasks tab is totally empty, proceed as Erik suggested.
If you don't want to upgrade to BOINC rev 6, you can also upgrade to 5.8.16 (a version still without separate data directory). To get it, click the All versions link in the window Erik linked to.
Gruß,
Gundolf
Computer sind nicht alles im Leben. (Kleiner Scherz)
Does anyone ever had a task
)
Does anyone ever had a task failing just because of a Core Client update? I vaguely remember such things from the 4.x series and occasionally development versions, but have not seen anything like that with recommended versions since back then.
I usually just download & install a new Core Client even if the old one is still running. Only on Linux I bother terminating the older one first, on Windows & Mac I leave that to the installer.
Maybe I'm a bit too lazy, but I don't care much even if I get one or two failing tasks.
BM
BM
RE: RE: ...Tap the
)
Ah, you are correct Gundolf Jahn. My apologies if I led anyone wrong, I just recent (late last month) got back into BOINC/Einstein and time has me befuddled apparently.
RE: Does anyone ever had a
)
After giving it some more thought with your post in mind, I believe you are correct. I realize now that I was thinking of losing tasks when forcing application changes (a la Akos Fekete back in the day).
So much fail today.... I'll go put my nose into a corner now.
fyi : The reason why I used
)
fyi : The reason why I used 4.19 on one box so long has been trouble with the proxy authentication. 4.19 had Berkeley code for that, later versions used the curl library. Not much lost, it's just an old and inefficient P4.