Tabula Rasa in Boinc-Folder for new S5R5 Einstein-Run
12 Jan 2009 15:38:58 UTC
Topic 194133
(moderation:
I have closed Boinc and deleted the entire einstein-folder. Past a restart Boinc is writing in message-log:
file projects/einstein.phys.uwm.edu/Config_L_S4lD not found
file projects/einstein.phys.uwm.edu/config_S4R2a.cfg not found
file projects/einstein.phys.uwm.edu/config_S5R1a.cfg not found
file projects/einstein.phys.uwm.edu/config_S5RIa.cfg not found
I know this files was needed in the past but why Boinc downloading this files now? Resetting the project didn't help.
Tabula Rasa in Boinc-Folder for new S5R5 Einstein-Run
)
To prepare for S5R5, you have to delete nothing, except if you have a app_info.xml file for beta-testing an app which you should erase after finishing current work.
Boinc keeps a list of files that it downloaded and it will re-download those if the files happen to vanish from your systems. Those CONFIG files are really not needed anymore, but they are tiny and don't do any harm. If you insist, you could remove references to them from the client_state.xml file of your BOINC installation (AFTER stopping boinc), but if you are not used to editing XML files manually, then you probably want to leave that file alone.
CU
Bikeman
Yes I had testing
)
Yes I had testing beta-6.10.
Manually editing the client_state.xml-file was not my intent.
I thought that Boinc will clear all unnecessary stuff if i resetting this project. I believe before Einstein changed to the new S5R5-run it will be a good idea to clear out the boinc-server-directory from all old files.
PS: My boinc-inst also tried to download some (!)S5R2-files and give up.
RE: Yes I had testing
)
To clear out all the garbage, you would probably need to:
1. Set NNW and run out work for all projects you are attached to
2. Detach from all Projects
3. Uninstall BOINC
4. Delete the BOINC folder and all sub-folders
5. Reinstall BOINC
6. Reattach to all projects
Seti Classic Final Total: 11446 WU.
RE: To clear out all the
)
Woa, that's heavy!
If you really want to do that (it's not necessary, just ignore the superfluous files) then you should at least save all account*.xml files before step 2 and restore them instead of step 6.
Gruß,
Gundolf
Computer sind nicht alles im Leben. (Kleiner Scherz)
RE: RE: To clear out all
)
No. One of the objectives is to stop re-downloading all those superfluous files after they've been deleted. If you save the account*.xml files, then the entries for those superfluous files will still be there and they'll be downloaded again.
However, I just ignore them myself.
Seti Classic Final Total: 11446 WU.
RE: No. One of the
)
There's not one entry in the account_*.xml files, so it's impossible that they cause downloading of any files. They only contain information concerning the account authenticator, resource share and GUI URLs.
Gruß,
Gundolf
Computer sind nicht alles im Leben. (Kleiner Scherz)
RE: No. One of the
)
As Gundolf has mentioned, the account files shouldn't be deleted. In fact there is only one way to stop old unneeded files from being re-downloaded and that is to remove the block from the state file, client_state.xml. The drastic way is to do something that clobbers the state file completely like resetting or detaching. The smart way is listed as a series of steps below.
project folder, identify those known old files you wish to delete
* Check (in your BOINC folder using an editor) to see if there are blocks listing each of these old files in your state file.
* If there aren't you can simply delete the old files in your project folder
* If there are entries you have to do two things - delete the entry in the state file and delete the file itself in the project folder
* Of course, you need to stop BOINC before editing the state file, restarting afterwards.
Cheers,
Gary.
RE: PS: My boinc-inst also
)
Hm. I'm currently looking into the data file deletion stuff on the server side (scheduler), but the behavior you describe looks like a bug in the Client. Honestly I don't know whether there is a Client version that doesn't have this.
I'd suggest detaching from Einstein@home and then attaching again, though I have seen Clients that don't clean up all project information when detaching.
If you don't want to got through the attach process again manually you could save a copy of account_einstein_phys_uwm.xml file from your BOINC folder somewhere, detach from the project (deleting the original file) via the Manager, drop the account file backup back in the BOINC folder and stop & start the Client. This should automatically re-attach to Einstein@home.
BM
BM
Okay, maybe a bug in the
)
Okay, maybe a bug in the client.
My solution is to change the connection from directline to thru a proxy-server and there to deny to load that stuff. Deleting all old stuff and restart boinc. Boinc writes a message to the log "temporary failure to download" and boinc has two buttons with something like "restarting a download" and "cancel". If you hit the cancel-button you will get a message like "are you sure - yes/no" and give up.
Now, i have cleaned client_state.xml-files :D
PS: If i could editing my OP, i would write [solved] on first position of subject-line.