![]() 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. (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. Please share with us what solved the issue if ever you experienced this problem if the above does not.By setting them at the host, they will automatically be set for every jail as well. ** Basic instruction on using the Simple view and Advanced view you find in the BOINC Manager official wiki. Provide as much information as you can of what was already done, so we can eliminate these from things to check. If no solution is found, posting the Message log detail from the Client where it starts to attempt to communicate all the way to the end of the message log will allow support to analysis the problem. Ultimately a proper shutdown and restart of the computer may solve the issue. Expired DNS (IP) information BOINC is (depending on version) still remembering, could be the cause. Hibernating or putting a device in Standby has for some caused hanging. Warning: Detaching looses all work in progress for this project! If not correct, detach from WCG in the Project Tab of BM and reattach via the Tools menu Attach to Project by selecting WCG from the drop down list and entering your member name and password.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |