INSTALLATION MANUALL: Gentoo
============================
The fci-client runs on Linux, FreeBSD, OpenBSD, Mac OS X and Windows,
the fci-server runs on Linux, and on FreeBSD & OpenBSD using Linux emulation.
The fci-client sends data from a client to the fci-server, among which are the
output of Dick Howells qd, Operating System and Hardware information and the
most interesting files in the Folding@Home client directory.
The server does almost all processing, and uses various tools to do it.
The tools uses by the FCI server are:
- xyz2pdb
- rasmol
- convert (from media-gfx/imagemagick)
- htpasswd (from Apache)
convert and htpasswd should be installed before FCI is.
xyz2pdb is shipped with FCI, just like Dick Howells qd is. xyz2pdb is used to
convert the current.xyz to a .pdb which is fed to rasmol.
A 32 bit Linux binary of rasmol is also shipped, but many Linux distros and
FreeBSD have native packages of rasmol. Gentoo has rasmol in portage
(sci-chemistry/rasmol), so the rasmol binary shipped with FCI will not be
installed. Rasmol is used to generate an image and/or animation of the
projects in the current.xyz which the clients upload.
convert is part of media-gfx/imagemagick, it's used to compile animations out
of multiple rasmol generated images.
Installing on Linux: Gentoo
---------------------------
The installation process described in this document assumes that you're running
a Gentoo 2008.0, 10.0 or later system, on which it has also been tested.
The fci-client has very few dependencies, the fci-server has a bit more:
Perl Module | Gentoo Package
------------------------+-----------------------
Installer: |
- XML::Simple | dev-perl/XML-Simple
- Getopt::Mixed | dev-perl/Getopt-Mixed
- Date::Calc | dev-perl/Date-Calc
|
Client: |
- LWP::UserAgent | dev-perl/libwww-perl
- HTTP::Request::Common | dev-perl/libwww-perl
- Date::Calc | dev-perl/Date-Calc
- XML::Simple | dev-perl/XML-Simple
- Getopt::Mixed | dev-perl/Getopt-Mixed
Application | Gentoo Package
------------------------+-----------------------
Client: |
- lsb_release | sys-apps/lsb-release
- lspci | sys-apps/pciutils
|
Server: |
- convert | media-gfx/imagemagick
- rasmol | sci-chemistry/rasmol
- bunzip2 | app-arch/bzip2
|
- Apache 2.x webserver | www-servers/apache
- Apache2 mod_perl | www-apache/mod_perl
Perl Module | Gentoo Package
------------------------+-----------------------
Server: |
- LWP::UserAgent | dev-perl/libwww-perl
- Date::Calc | dev-perl/Date-Calc
- Date::Manip | dev-perl/DateManip
- Date::Format | dev-perl/TimeDate
- XML::Simple | dev-perl/XML-Simple
- Data::Dumper | perl
- Apache::Htpasswd | g-cpan
- Getopt::Mixed | dev-perl/Getopt-Mixed
- MIME::Lite | dev-perl/MIME-Lite
- GD::Graph | dev-perl/GDGraph
- Image::Magick | media-gfx/imagemagick
- Mail::RFC822::Address | g-cpan
- HTML::Entities | dev-perl/HTML-Parser
- RRDs | net-analyzer/rrdtool
- Math::Round | dev-perl/Math-Round
|
Server with Apache 2.x: |
- Apache2::Request | www-apache/libapreq2
- Apache2::Upload | www-apache/libapreq2
Before you can use install.pl to install the FCI client and/or server, first
install the dependencies:
# FCI Installer only:
emerge dev-perl/XML-Simple dev-perl/Getopt-Mixed dev-perl/Date-Calc
# FCI Client only:
emerge dev-perl/libwww-perl dev-perl/Date-Calc dev-perl/Getopt-Mixed \
sys-apps/lsb-release sys-apps/pciutils dev-perl/XML-Simple
# FCI Server only:
You need to add 'svg' to your USE flags in /etc/make.conf to build rrdtool.
You need to add 'png' to your USE flags in /etc/make.conf to build gd
properly, otherwise GD::Graph may complain with the following error:
Can't locate object method "png" via package "GD::Image"
emerge www-apache/libapreq2 www-servers/apache www-apache/mod_perl \
dev-perl/libwww-perl dev-perl/Date-Calc dev-perl/XML-Simple \
dev-perl/Getopt-Mixed dev-perl/MIME-Lite dev-perl/GDGraph \
media-gfx/imagemagick dev-perl/DateManip sci-chemistry/rasmol \
dev-perl/HTML-Parser dev-perl/TimeDate net-analyzer/rrdtool \
app-arch/bzip2
rc-update add apache2 default
There is an ebuild for Math::Round but it's masked, install it overriding mask:
emerge /usr/portage/dev-perl/Math-Round/Math-Round-0.06.ebuild
There are no ebuilds for some modules used by the FCI server, but you can get
them from CPAN using g-cpan:
emerge app-portage/g-cpan
g-cpan -i Apache::Htpasswd
g-cpan -i Mail::RFC822::Address
After installing apache, make sure that "-D PERL -D APREQ" is added to
APACHE2_OPTS in /etc/conf.d/apache2 so that mod_perl and libapreq2 are
loaded when apache starts up.
After the dependencies have been installed, run the installer to install the
FCI client and/or server:
# FCI client only
./install.pl --client
# FCI server only
./install.pl --server --owner <user> --group apache
# FCI client & server:
./install.pl --client --server --owner <user> --group apache
The owner of the FCI server files should be your regular user account, you
being the FCI server administrator. You shouldn't need root privileges to
run the FCI server scripts, it's enough to have your regular user account
be a member of the apache group.
The installer does require root privileges, and has several options which
you can use to customize the installation, overriding the built-in defaults:
./install.pl --help
Folding@Home Client Info Installer v1.0
Usage: install.pl [--client|--server] [OPTIONS]
Options:
-c, --client Install the client component
-s, --server Install the server component (Linux only)
-b, --bin-dir <PATH> Path of executable files (/usr/local/bin/)
-n, --conf-dir <PATH> Path of configuration files (/usr/local/etc/fci/)
-d, --data-dir <PATH> Path of the data files (/usr/local/share/fci/)
-w, --www-dir <PATH> Path of the website files (/var/www/fci/)
-o, --owner <NAME> Username to own the website files (root)
-g, --group <NAME> Username to own the website files (www-data)
-f, --force Install files & directories even if they already exist
-v, --verbose Enable verbose output
-h, --help Print this usage information
Installing the FCI client using ./install --client comes down to the following:
copy client/qd -> /usr/local/bin/qd
copy client/qdinfo.dat -> /usr/local/share/fci/qdinfo.dat
copy client/fci-client.pl -> /usr/local/bin/fci-client.pl
It installs the fci-client Perl script, and a copy of qd and its data file
qdinfo.dat for inital use by fci-client.pl. The FCI client will automatically
download the latest qdinfo.dat from the FCI server before every upload, it's
stored in its own per-user cache: ~/.fci/. A more recent revision of the qd
binary is only downloaded if the client is run with --update-qd. New revisions
of qd may contain bugfixes or new features you may want to have available to
your FCI client, but automatic download of the most recent qd binary from the
FCI server might overwrite a custom compiled binary in ~/.fci/, which is not
desirable.
The FCI client should now be ready to perform uploads to the server. It is
recommended to use the --verbose argument to fci-client.pl the first time the
FCI client command is tested for use. By default fci-client.pl doesn't display
any output unless it encounters an error, but the verbose output contains all
the information you need to verify its correct operation.
The fci-client.pl script needs to be scheduled to run periodically. To spread
the load on the server, it's recommended to use slightly different times for
the client uploads if there are many clients on a single server and/or the
server doesn't have many resources in terms of bandwidth, RAM or CPU power.
Add a rule like the one below to the crontab of the user who also runs the
Folding@Home client:
### crontab rules for FCI client ###
10 * * * * /usr/local/bin/fci-client.pl --dir /home/folding/ --url http://example.com/fci/index.pl
### crontab rules for FCI client ###
Installing the FCI server using ./install --server comes down to the following:
mkdir /var/www/fci
copy www/* -> /var/www/fci/
copy scripts/* -> /usr/local/bin/
copy bin/* -> /usr/local/bin/
chmod -R <user>:apache /var/www/fci/
It creates a directory where the server files are stored, this includes the
mod_perl scripts, XML and qd files, etc. The scripts and programs which comprise
the FCI server are installed, and the paths of these tools are updated in the
FCI server configuration: /var/www/fci/settings/site-data/config.xml
If /usr/bin/rasmol or /usr/local/bin/rasmol already exist the rasmol binary
shipped with FCI is not copied (unless --force is used), and the existing
rasmol will be used.
The xyz2pdb binary shipped with FCI will be copied to /usr/local/bin/ only if
it doens't exist yet (unless --force is used).
The installer will look for the convert and htpasswd binaries in /usr/bin/ and
/usr/local/bin. If convert of htpasswd are not found the installer will quit.
You can create a symlink to the convert or htpasswd binary in another location
and rerun the installer, or you can create empty file instead of a symlink.
It's recommended to set the path to the real convert or htpasswd binary using
the Settings web interface after the install has completed.
The Apache webserver still needs to be configured for FCI, before it can accept
uploads from an FCI client.
You can create the file /etc/apache2/vhosts.d/99_fci.conf using the below
configuration:
### /etc/apache2/vhosts.d/99_fci.conf ###
# FCI apache configuration
Alias /fci /var/www/fci
<Directory /var/www/fci/>
DirectoryIndex index.pl
<FilesMatch "^index\.pl$">
SetHandler perl-script
PerlHandler ModPerl::Registry
Options +ExecCGI
PerlOptions +GlobalRequest
</FilesMatch>
AllowOverride AuthConfig
# Disallow access to the Perl components
<FilesMatch "\.plc$">
deny from all
</FilesMatch>
Options -Indexes +FollowSymLinks
Order allow,deny
Allow from all
</Directory>
### /etc/apache2/vhosts.d/99_fci.conf ###
Reload apache to load the FCI configuration:
/etc/init.d/apache2 reload
The rasmol binary shipped with Gentoo in /usr/bin/rasmol is actually a wrapper
script, use the FCI Settings web interface to update the path of rasmol to:
/usr/lib/rasmol/rasmol.32
It is strongly advised to use the Settings webinterface to configure HTTP
authentication for: client uploads, the client data files and the Settings
webinterface itself.
Now the FCI server should be readly to accept uploads from FCI clients.
The collection of scripts which were installed as part of the FCI server,
need to be scheduled to run periodically. And the order in which they run is
significant. Each script acquires and/or processes a specific subset of the
Folding@Home data, this data is processed into the XML files used by the FCI
server.
Add rules like the ones below to the crontab of the user who owns the FCI
server files:
### crontab rules for FCI server ###
0 * * * * /usr/local/bin/fci-update-stanford-files.pl --dir /var/www/fci/
5 * * * * /usr/local/bin/fci-update-qd-files.pl --dir /var/www/fci/
15 * * * * /usr/local/bin/fci-update-fahstats.pl --dir /var/www/fci/
#15 * * * * /usr/local/bin/fci-jmol-missing-projects.pl --dir /var/www/fci/
30 * * * * /usr/local/bin/fci-update-xml-files.pl --dir /var/www/fci/
35 * * * * /usr/local/bin/fci-generate-queue-graphs.pl --dir /var/www/fci/
35 * * * * /usr/local/bin/fci-update-jmol-projects.pl --dir /var/www/fci/
40 2,5,8,11,14,17,20,23 * * * /usr/local/bin/fci-update-eoc-stats.pl --dir /var/www/fci/
45 * * * * /usr/local/bin/fci-update-project-images.pl --dir /var/www/fci/
### crontab rules for FCI server ###
What each individual script does and how it relates to the other scripts is
described in more dept below:
fci-update-stanford-files.pl
It can be run independently, it doesn't share files with other scripts which
need to be considered. It downloads the HTML and text files from Stanfords
webserver, which are parsed by fci-update-xml-files.pl. Empty copies of these
files (except the team<N>.txt files) are shipped with FCI, but these need to
be updated with the lastest copy from Stanford first.
fci-update-qd-files.pl
It can be run independently, it doesn't share files with other scripts which
need to be considered. It download the latest qd binaries and qdinfo.dat
which the server will make available to the clients.
fci-update-fahstats.pl
It needs to run after fci-update-xml-files.pl has run, because it uses the
username-list.xml file which fci-update-xml-files.pl updates. It retrieves
the UserID for each username listed in the fahstats.com database.
fci-jmol-missing-projects.pl
It needs to run after fci-update-xml-files.pl has run, because it uses the
known-projects.xml file which fci-update-xml-files.pl updates. It checks for
projects Jmol is missing the current.xyz file for, the file is emailed if a
missing project is found in the known-projects.xml file.
fci-update-xml-files.pl
It's the main update script. It processes the uploaded data of the clients,
the downloaded data from Stanford, EXTREME Overclocking, fahstats.com and
Jmol. It updates the XML files which are used by the web interface and some
of the other FCI scripts.
fci-generate-queue-graphs.pl
It needs to be run closely after fci-update-xml-files.pl is finished. It
generates graphs of the average PPD of the Work Units in the queue. It uses
the client-list.xml file which fci-update-xml-files.pl updates.
fci-update-jmol-projects.pl
It needs to run after fci-update-stanford-files.pl has run, because it uses
the project-summary.xml which fci-update-stanford-files.pl updates. It
downloads the latest fah-projects.xml from Jmol, its data is used to link
to the Jmol webpage from a project page and to add projects which Jmol knows
about to the project-summary.xml if we don't known about it from
fci-update-stanford-file.pl yet (which uses Stanfords psummary.html to update
project-summary.xml).
fci-update-eoc-stats.pl
It needs to run after fci-update-xml-files.pl has run, because it uses the
username-list.xml file which fci-update-xml-files.pl updates. It downloads
the XML stats for each username listed.
fci-update-project-images.pl
It needs to run after fci-update-xml-files.pl has run, because it uses the
known-projects.xml file which fci-update-xml-files.pl updates. It generates
the missing image types for each known project.
|