| | 1 | = Creating installers for Linux = |
| | 2 | |
| | 3 | The recommended actions of a BOINC installer for Linux: |
| | 4 | |
| | 5 | * Create a user 'boinc' and group 'boinc' if they don't already exist. All files and directories created by the installer should have this owner and group. |
| | 6 | * Install the executables (boinc, boincmgr, boinccmd) in the appropriate directory. |
| | 7 | * Create a directory /var/lib/boinc-client |
| | 8 | * Create a directory /etc/boinc-client/. Within it, create a file config.properties containing |
| | 9 | {{{ |
| | 10 | data_dir=/etc/boinc-client/config.properties |
| | 11 | }}} |
| | 12 | |
| | 13 | You then have a choice: |
| | 14 | |
| | 15 | * Public installation: create an empty file /var/lib/boinc-client/gui_rpc_auth.cfg. The installing user will immediately be able to run the Manager and attach to a project or account manager. But so will any other user. When they run the Manager they'll get a notice saying that other users can control BOINC, and directing them to [https://boinc.berkeley.edu/gui_rpc_passwd.php a web page] telling them how to changes this if they want. |
| | 16 | * Private installation: don't create such a file. If the installing user runs boincmgr, they'll get an error message directing them to [https://boinc.berkeley.edu/gui_rpc.php a web page] telling them to add themselves to the 'boinc' group. |
