![]() ![]() If you're running several projects on the same server and want to isolate them from each other, you can create a different user and group for each project, and add apache or www-data to all of the groups. ![]() You may also need to change the ownership of these directories and all their subdirectories to boincadm/boinc. To fix permissions on an existing project, do: ![]() When you create a BOINC project using make_project, the critical directories are owned by boincadm and have the set-GID bit set this means that any directories or files created by apache or Thus, both boincadm and apache or www-data will have read/write access to all directories and files, but other users will have no access. (the "566" is the group ID it may be different on your system).Īpache will need to be restarted for this to take effect.īoth boincadm and apache or Normally you can use a umask of 0002 or 0007. To solve this problem on Debian or Ubuntu, add www-data to the to group boincadm using In the following we'll assume that the project owner is boincadm, with primary group boincadm.īy default, the directories created by the apache web server user (on Fedora this is user ' apache' on Ubuntu or Debian it's ' To solve this problem on Fedora, add apache to the to group boincadm using The project owner may be your existing account, or you can create a new account for this purpose with useradd. Other programs run under a normal user account, called the "project owner".The scheduler, file upload handler, and web software run under the web server account (on Fedora this is user ' apache' on Debian it's ' www-data').Installing the BOINC server on Unix Groups and permissionsīOINC server programs run as two different users: Info on increasing capacity and reliability is here. Make it secure turn off any unneeded network services, especially those that use plaintext passwords (like FTP or Telnet).Put it behind a firewall allow access via port 80 (HTTP) and optionally 443 (HTTPS).Do whatever you can to make it highly reliable (UPS power supply, RAID disk configuration, hot-swappable spares, temperature-controlled machine room, etc.).Your server should have 64-bit processors, at least 8 GB of RAM, and at least 40 GB of free disk space.Your Internet connection should have adequate performance and reliability.Your server must have a static IP address.Before deploying a project more widely, make sure that your server has adequate performance, availability, and security. General instructions are given below, followed by a cookbook for setting up a BOINC server on a Debian system.įor experimentation and debugging, you can use almost any computer as a BOINC server. You can use any Unix system as a BOINC server we recommend using a recent Linux release. Build BOINC from source on your own system.Debian and Ubuntu offer a "boinc-server-maker" package to create BOINC projects more easily on local or remote machines.Use a set of Docker containers developed by Marius Millea.If you choose to use your own hardware, there are several software options: You'll have to pay, but it may be cheaper than using your own hardware. The hardware and most of the software issues are taken care of for you. You can set up a BOINC server in a commercial cloud, such as Amazon or Google. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |