Questions and Answers :
Unix/Linux :
boinc client version 4.19
Message board moderation
Author | Message |
---|---|
Send message Joined: 4 Oct 04 Posts: 4 Credit: 2,488,649 RAC: 5,870 |
Other boinc applicataions have upgraded to 4.19, is running it going to cause problems with climateprediction? Geoffrey |
Send message Joined: 15 Nov 04 Posts: 19 Credit: 35,499 RAC: 0 |
When I started a new computer with CPDN recently, it dl'ed 4.19, so I assume no there is no problem running it. But it might be a good idea to backup your boinc directory if you switch the program half-way through. Better safe than sorry ;-) |
Send message Joined: 6 Aug 04 Posts: 65 Credit: 1,605,224 RAC: 0 |
> When I started a new computer with CPDN recently, it dl'ed 4.19, so I assume > no there is no problem running it. But it might be a good idea to backup your > boinc directory if you switch the program half-way through. Some people (myself included) like to wait till either the end of a model run or the end of a phase before doing upgrades but make a backup as mentioned, just in case. |
Send message Joined: 18 Nov 04 Posts: 3 Credit: 4,069 RAC: 0 |
> > When I started a new computer with CPDN recently, it dl'ed 4.19, so I > assume > > no there is no problem running it. But it might be a good idea to backup > your > > boinc directory if you switch the program half-way through. > > Some people (myself included) like to wait till either the end of a model run > or the end of a phase before doing upgrades but make a backup as mentioned, > just in case. > Why do you wait for the end of a model run? Will the upgrade affect the model I am running? |
Send message Joined: 7 Aug 04 Posts: 2185 Credit: 64,822,615 RAC: 5,275 |
> Why do you wait for the end of a model run? Will the upgrade affect the model > I am running? > > It shouldn't, and it hasn't for most people, but previous upgrades have occasionally caused a premature model upload. So, if people are far along in their models and have put several hundred hours into them, they are somewhat reticent to upgrade, even if there is only a small chance of a problem. If you do upgrade: Suspend and Exit the currently running model. Some people make a backup of the BOINC folder in case something goes wrong. Run the new 4.19 setup executable and overwrite the BOINC directory. Restart BOINC and it should start up where it left off. |
Send message Joined: 17 Aug 04 Posts: 753 Credit: 9,804,700 RAC: 0 |
The other factor is that there is a major upgrade of BOINC scheduled in the next couple of weeks. That looks as though it will be more of an issue, but if you are having no problems with the current version you might want to wait for the 4.2x version and reassess, especially in Linux. |
Send message Joined: 18 Nov 04 Posts: 3 Credit: 4,069 RAC: 0 |
> > Why do you wait for the end of a model run? Will the upgrade affect the > model > > I am running? > > > > > It shouldn't, and it hasn't for most people, but previous upgrades have > occasionally caused a premature model upload. So, if people are far along in > their models and have put several hundred hours into them, they are somewhat > reticent to upgrade, even if there is only a small chance of a problem. If > you do upgrade: > > Suspend and Exit the currently running model. > Some people make a backup of the BOINC folder in case something goes wrong. > Run the new 4.19 setup executable and overwrite the BOINC directory. > Restart BOINC and it should start up where it left off. > Just did the upgrade and all is well. Stopped boinc, removed the existing boinc executable from the boinc directory, dropped the new executable into the boinc directory (leaving everything else in there alone) and started it again. The log shows that the new version was detected and it picked up where the previous version left off. Also noticed the log was 27MB, so added it to the lograte configuration for good measure. ttfn Steve |
Send message Joined: 6 Aug 04 Posts: 9 Credit: 5,061 RAC: 0 |
Oops. I should've put this in the OSX area, I followed a link from there to this thread without noticing the difference in platforms. Move if appropriate, hosts, please. I did the same thing (got 4.19, dropped it in place of 4.13, called it from within the Terminal window I'd halted, as you can see in quoted stuff); with OSX; here's the result with my question whether I'm getting expected results from the calculations that are getting repeated: interrupted with control-C ^C 2005-02-13 10:57:12 [---] Received signal 2 2005-02-13 10:57:13 [---] Exit requested by user > dropped the new release of the application into /Applications, dragged icon to paused Terminal > The new version was detected Hank:~ hank$ /Applications/boinc_4.19_ppcG3 2005-02-13 10:58:42 [---] Starting BOINC client version 4.19 for powerpc-apple-darwin 2005-02-13 10:58:42 [climateprediction.net] Project prefs: no separate prefs for home; using your defaults 2005-02-13 10:58:42 [---] Version Change Detected (4.13 -> 4.19); running CPU benchmarks 2005-02-13 10:58:42 [climateprediction.net] Host ID is 91254 2005-02-13 10:58:42 [---] General prefs: from climateprediction.net (last modified 2004-08-09 08:46:08) 2005-02-13 10:58:42 [---] General prefs: no separate prefs for home; using your defaults 2005-02-13 10:58:42 [---] Running CPU benchmarks 2005-02-13 10:59:43 [---] Benchmark results: 2005-02-13 10:59:43 [---] Number of CPUs: 1 2005-02-13 10:59:43 [---] 779 double precision MIPS (Whetstone) per CPU 2005-02-13 10:59:43 [---] 1447 integer MIPS (Dhrystone) per CPU 2005-02-13 10:59:43 [---] Finished CPU benchmarks 2005-02-13 10:59:44 [climateprediction.net] Resuming computation for result 3p7q_100194380_1 using hadsm3 version 4.03 Starting model in /Users/hank/projects/climateprediction.net... Created shared memory region key = 25460 Env Used=DYLD_LIBRARY_PATH=/Users/hank/projects/climateprediction.net:../ Starting model ID 3p7q_100194380 Phase 1 Stack size=48.00 MB Waiting for model startup, this may take a minute... 3p7q_100194380 - PH 1 TS 033553 - 10/11/1812 00:30 - H:M:S=0129:04:33 AVG=13.85 DLT= 0.00 |
©2024 cpdn.org