Message boards : BOINC client : Moving BOINC data directory
Message board moderation
Author | Message |
---|---|
Send message Joined: 2 Dec 06 Posts: 9 |
I just installed BOINC 5.4.11 under Windows XP, as a service. I'd like to be able to keep the binaries under C:\\Program Files\\BOINC, and have the BOINC data under D:\\Data\\BOINC. Is this possible? I don't want to uninstall/reinstall BOINC to D:\\Data. This partition is for data, not applications. Leaving the data under C:\\Program Files\\BOINC is not workable for me, since I often image and restore that partition, and doing so could be very wasteful when completed work was overwritten. I have searched for an answer, and saw mention of the -dir parameter, but this does not seem to be a full answer to my problem. |
Send message Joined: 2 Dec 06 Posts: 9 |
In an effort to solve my own problem, I have tentatively made the following changes. I only post them here in case they are fully correct, in which case no one will need to bother to reply, or in case they are partially correct, and they might save someone the trouble of detailing all the steps. Again, this is not advice for anyone else, this is more along the lines of asking, "Can someone confirm the accuracy or stupidity of this?" 1. Stopped the BOINC service, and closed the BOINC Manager. 2. Went to HKEY_LOCAL_MACHINE\\SYSTEM\\CurrentControlSet\\Services\\BOINC and changed ImagePath from "C:\\Program Files\\BOINC\\boinc.exe" -daemon to "C:\\Program Files\\BOINC\\boinc.exe" -daemon -dir "D:\\Data\\BOINC". 3. Copied (could have moved) all .TXT, .XML, and .CFG files from C:\\Program Files\\BOINC to D:\\Data\\BOINC. Also copied the slots and projects directories (but left locale). 4. Started the BOINC service, and the BOINC Manager. So far, it seems to be working fine. But five minutes with this type of application doesn't mean too much. |
Send message Joined: 2 Dec 06 Posts: 9 |
I've learned that the following files are used by boincmgr.exe, and are to be left in the original* directory: gui_rpc_auth.cfg stderrgui.txt stdoutgui.txt The following files are used by boinc.exe, and should reside in the directory specified with the -dir parameter: stderrdae.txt stdoutdae.txt Everything else, for me, seems to be working fine as I laid out in the post above. ---- * I believe the directory in question is technically the EXE directory, and not the current directory, when boincmgr.exe is running. I say this because I tried changing the Start in field of the boincmgr.exe shortcut, which serves to specify the current directory. It didn't work--boincmgr.exe still required the files to be in the EXE directory. Suffice it to say...don't bother moving the files mentioned. |
Send message Joined: 8 Jan 06 Posts: 448 |
Interesting. What happens when you try to upgrade? You will probably need to reapply your registry hack! Boinc V 7.4.36 Win7 i5 3.33G 4GB NVidia 470 |
Send message Joined: 2 Dec 06 Posts: 9 |
Yes, I will need to reapply the registry value change, but this is no big deal. I have a REG file that is automatically imported each time I log off (and manually, if desired). This way, I can automatically deal with lots of issues that would otherwise be really annoying (such as applications that insist on adding their own Run value, or the taking over of file associations). It would also be no big deal to make a one-off REG file for just this one value. On another note: I've encountered one problem [Edit: Solved; see below]. It seems that gui_rpc_auth.cfg is created/updated by the boinc.exe service each time it starts, and this file is placed in the -dir directory. However, boincmgr.exe seems to insist on making the installation directory (C:\\Program Files\\BOINC) the current directory, and so it looks for gui_rpc_auth.cfg there--however, that copy is not in sync with the other one, so boincmgr.exe does not successfully connect to boinc.exe. I just noticed this problem, and have no doubt I can solve it soon. (I was wrong about the Start in field for the shortcut of boincmgr.exe--even when that field is changed, boincmgr.exe makes the install directory the current directory. The same is true if you run boincmgr.exe from a batch file, using the /D parameter to change the currdir. Hrmf.) ---- Workaround: A command script (.CMD file) with these two simple lines: if exist "D:\\Data\\BOINC\\gui_rpc_auth.cfg" copy /v "D:\\Data\\BOINC\\gui_rpc_auth.cfg" "C:\\Program Files\\BOINC" start "" "C:\\Program Files\\BOINC\\boincmgr.exe" /s |
Send message Joined: 2 Dec 06 Posts: 9 |
Certainly my shortcut with the '-dir D:\\BOiNCData' has kept it running from that place....5 minutes or 5 hours..... what's the difference. Potentially a big difference, since sometimes problems only become apparent after a period of time. But at this point, I'm quite confident that the steps I've outlined above are workable. Since I'll be starting a grid team, I'm going to eventually put these steps in a better format. |
Send message Joined: 23 Dec 06 Posts: 14 |
Since I'll be starting a grid team, I'm going to eventually put these steps in a better format. Please do. I'm about to make a generic image for the new workstations here. If I know where the dirs are, and what files are needed where, then I can get it setup just fine. AdvTHANKSance |
Send message Joined: 2 Dec 06 Posts: 9 |
The instructions are pretty simple and are above. If boinc.exe has been run at all since having been installed, follow the steps 1-4, but don't bother moving these files from where they originate, in the BOINC installation directory: gui_rpc_auth.cfg stderrgui.txt stdoutgui.txt Create the desired data directory, move existing data (slots and projects directories), change the applicable registry value, and create the batch file to run boincmgr.exe. If you have a fresh BOINC install on your hands (i.e. boinc.exe hasn't been run at all since being installed, and no data or configuration files exist), then all you have to do is step 2 (the registry value change), and create the batch file for boincmgr.exe. |
Copyright © 2025 University of California.
Permission is granted to copy, distribute and/or modify this document
under the terms of the GNU Free Documentation License,
Version 1.2 or any later version published by the Free Software Foundation.