Message boards : Questions and problems : A No Reboot Install, with automatic attachment and credentials possible?
Message board moderation
Author | Message |
---|---|
Send message Joined: 25 Sep 08 Posts: 1 ![]() |
I've been bouncing around the wiki and the forums trying to determine if it's possible, and how to implement it if so, to create a custom install that will be: 1) Silent 2) automatically attach to rosetta@home 3) Automatically login to rosetta@home with a given set of credentials. 4a) Not require a reboot. 4b) Install as a service. Option 4a and 4b would be two separate installers. I think I've gotten on the right track http://boinc.berkeley.edu/wiki/Deploying_BOINC_on_networks#Appendix_B but I can't figure out how to set the project and the credentials (if that's even possible via this route), and I have yet to find any idea as to how to install sans the reboot. Cheers! |
![]() Send message Joined: 3 Apr 06 Posts: 547 ![]() |
2) automatically attach to rosetta@home You can add the ...\BOINC\account_boinc.bakerlab.org_rosetta.xml (or how is its exact name) and copy it into the BOINC data folder during installation. After the client starts, it will immediately attempt to communicate with Rosetta's project servers to attach the host to it. These computers will "crunch for the person", who's account key is stored in the account_xxxxxxxx.xml files. If the computers will be publicly accessible, you should consider putting the weak account key in - but well, Rosetta's older web software does not yet seem to generate it :-( This probably correlates with project_init.xml config file, but I do not know exactly how - possibly the installer creates related account_xxxxx.xml files? Otherwise I'm not very sure, what you mean with login [...] with a given set of credentials and to set the project and the credentials, but you'll sure explain ;-) Peter |
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.