Changes between Version 53 and Version 54 of ServerIntro

Timestamp:

Apr 1, 2009, 2:26:31 PM (15 years ago)

Author:

Nicolas

Comment:

some formatting tweaks to permissions section

ServerIntro

@@ -36 +36 @@
  * BOINC daemons runs as whoever created the project (let's say user '`boincadm`', group '`boinc`'). '''Do not run BOINC daemons (or anything else) as root'''.
 
-By default, the directories created by user apache are not world-writable. This causes problems: for example, when the file upload handler creates a directory in the [DirHierarchy upload hierarchy], it's owned by (apache, apache), and the [FileDeleter file deleter] (which runs as `boincadm`) won't be able to delete the files there.
+By default, the directories created by user `apache` are not world-writable. This causes problems: for example, when the file upload handler creates a directory in the [DirHierarchy upload hierarchy], it's owned by (`apache`, `apache`), and the [FileDeleter file deleter] (which runs as `boincadm`) won't be able to delete the files there.
 
 To solve this problem, edit `/etc/group` so that `apache` belongs to group `boinc`, i.e. the line:
@@ -54 +54 @@
 }}}
 
-When you create a BOINC project using [MakeProject 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 in those directories will have group `boinc` (not group `apache`). The BOINC software makes all directories group read/write. Thus, both `apache` and `boinc` will have read/write access to all directories and files, but other users will have no access.
+When you create a BOINC project using [MakeProject 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` in those directories will have group `boinc` (not group `apache`). The BOINC software makes all directories group read/write. Thus, both `apache` and `boinc` will have read/write access to all directories and files, but other users will have no access.
 
 To fix permissions on an existing project, do:
@@ -69 +69 @@
 You may also need to change the ownership of these directories and all their subdirectories to `boincadm/boinc`.  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` to all of the groups.
 
-When serving your project files from Apache, note that all directories up to and including the html directory must have execute permissions.  For example, if you use make_project to create the project template in your home directory, your home directory must have 711 permissions as opposed to the default of 700. If this is not corrected, you will receive a '''403 Forbidden''' error when attempted to browse to your project page. See [http://httpd.apache.org/docs/1.3/misc/FAQ.html#forbidden more information on dealing with Apache permissions problems].
+When serving your project files from Apache, note that all directories up to and including the `html` directory must have execute permissions.  For example, if you use `make_project` to create the project template in your home directory, your home directory must have 711 permissions as opposed to the default of 700. If this is not corrected, you will receive a '''403 Forbidden''' error when attempted to browse to your project page. See [http://httpd.apache.org/docs/1.3/misc/FAQ.html#forbidden more information on dealing with Apache permissions problems].
 
 === Installing BOINC software === #installing