If not, it's probably a bug on the project's part and you'll have to report that to them. Whether or not you can see the progress of the task in VBox is up to the project.ĭepending on where the project is with regard to development, their application will communicate back to the BOINC client what's happening, which will then show in the Task tab in BOINC Manager. Most probably running a form of Scientific Linux. The general thing is that BOINC starts the Virtual Box environment, and that the science applications and tasks run in that environment. The only project detailing what you can expect is Test4Theory, but their method of how things are done can differ from how other projects use the technology. I cannot give you an answer on that, as I don't run any of the projects with VBox. You will have to ask at the project you're running or wanting to run, what to expect. Probably because this differs from project to project. Anyhow, I left this section in in case someone regularly performs pkg update/upgrade + pkg audit -F in their jails.While I used a specific example in my post, my real question is a general one: what is the order of events that one might expect to happen with the VirtualBox + BOINC combination? I could not find ANYWHERE an outline of what to expect. With that trick of installing boinc-client via pkg before it was only one or two packages beeing updated (for some reason) but I don't remember which. During the second run of pkg update/upgrade a dozen packages got upgraded. As a result my jail spent 40+ minutes compiling everything boinc-client depends on.
At the very beginning of the tutorial I didn't do this trick of installing boinc-client via pkg. (e.g this works with my Fritzbox 7390)Ībout the second pkg update/upgrade.
AUTO LOAD BOINC LINUX PASSWORD
(If you're in a company or university you better put that key as it is into some password safe tool like keepassx)ĭepending on the DHCP-server you use, it should be possible to put in the name of the jail as hostname. But you can change the content of gui_rpc_auth.cfg and after a boinc-daemon restart, make use of a password you can remember easily. The only thing I discovered is an MRU-List for the hostname edit-field. I googled this BATCH=yes param and it seems that everybody is using it uppercase.Ībout the boinc-manager remembering the RPC password: I think it has just not been implemented. Thanks for your hints danb35, I adjusted the HowTo accordingly. I migrated this jail successfully to 9.10 stable. Any corrections, improvements and the like are most welcome! UNAME_r and OSVERSION do not agree on major version number The following links helped me on the journey: I am very refusive to set jail_sysvipc_allow=yes and so far its not needed I think) Once I had tasks having problems with shmget() but I just aborted them. (My boinc jail runs fine for quite a while now. Besides, I tried to put them directly at the Jail, which prevented the Jail from starting. Also put something like 'For BOINC' in the comment of the tunable, so that you remember later what it was for. I recommend to google every sysctl parameter before enabling it in the host. Its not just some option one can fiddle with. You can check that, by performing a 'sysctl _idprio' in the jail's root-shell.Īs always when one sets params like this, everybody has to make the decision themselves, whether its worth the risk. By setting them at the host, they will automatically be set for every jail as well.
0 kommentar(er)
