UbuntuHelp:FoldingJam/origami

文章出处:

https://help.ubuntu.com/community/FoldingJam/origami

点击翻译:

English

请不要直接编辑翻译本页，本页将定期与来源同步。

Overview

The test cases below are designed to confirm functionality on as many distributions as possible. Below I've outlined basic installation instructions for each major distribution. If you don't see your distribution listed, please find me in #ubuntu-folding on irc.freenode.net. Virtual Machines are perfect for this testing as the test focuses on distribution differences as opposed to hardware differences. The preferred version to use in testing is in bzr trunk on launchpad. Please checkout the latest revision using the command:

bzr branch lp:origami

If you don't have bzr installed, check to see if your distribution carries it and install using your package manager. The package is likely called bzr or bazaar. If it is not available (RHEL, CentOS for example), I suggest using the EPEL repository.

Install Tests

The below options outline standard install-time options. These should be tried one at a time as well as all at once. Please see the Pass / Fail section below if you are unsure how to verify a test. Example: Running a single test:

sudo origami install -u Zelut

Combined tests:

sudo origami install -u Zelut -t 45104 -p smp -c 1 -k <secret-key> -b big -P 8080 -H <ip>

note: if you do not have a 64bit installation you will not be able to test the -p option. note: if you do not have access to a web proxy (squid) you will not be able to test the -P and -H options.

Pass / Fail

Installation

origami install -u USERNAME:

This should install origami without any errors. You should be able to run 'origami status' and verify that Your Username matches that you assigned. Your Team should be set to 0.

origami install -t TEAMNUMBER:

This should install origami without any errors. You should be able to run 'origami status' and verify that Your Team matches that you assigned. Your Username should be set to Anonymous.

origami install -p smp or origami install -p amd64

This should install origami without any errors. This should use the 64bit folding client. This can be verified by ??? 'origami status' should also report that Your Username and Your Team are 0 and Anonymous. note: this requires a 64bit installation as well as the ia32-libs package (or your distributions equivalent).

origami install -c 1:

This should install origami without any errors. Your Username and Your Team should be 0 and anonymous. You can verify this test was successful by running the command:

sudo crontab -u origami -l

You should see something along the lines of:

# uncomment the cron entries below to automate starting and stopping the
# origami service during business hours

0 8  * * * /etc/init.d/origami stop &>/dev/null
0 17 * * * /etc/init.d/origami start &>/dev/null

If you see 'no crontab for origami' then this test has failed.

origami install -k PASSKEY:

This should install origami without any errors. Your Username and Your Team should be set to 0 and Anonymous. You can verify that this test was successful by:

grep '$PASSKEY' /var/lib/origami/foldingathome/CPU*/client.cfg

note: replace $PASSKEY with your actual PASSKEY.

origami install -b (small|normal|big):

This should install origami without any errors. Your Username and Your Team should be set to Anonymous and 0. You can verify that this test was successful by:

egrep '(small|normal|big)' /var/lib/origami/foldingathome/CPU*/client.cfg

If the result of the egrep command does not match the size option you specified during installation then this test has failed.

origami install -P port -H host:

This should install origami without any errors. This test requires that you have access to a proxy server, which you are defining the port and hostname for. If you do not have access to a proxy server you can skip this test. You can verify that this test is successful by:

egrep '(host|port)' /var/lib/origami/foldingathome/CPU*/client.cfg

If the result of the egrep command does not match the host and port that you specific during installation then this test has failed.

origami install -u USERNAME -t TEAMNUMBER -k PASSKEY -b (small|normal|big):

This should install origami without any errors. This test should define your preferred username, team number, define your passkey and define your WU size. You should be able to verify that all of these values were properly set by:

cat /var/lib/origami/foldingathome/CPU*/client.cfg

If any of the values you defined are not set in the output of the command above then this test has failed.

Test Results

NOTE: Please add your test results to the chart below. If you have successfully completed a section add a (./) mark, as well as your nick next to it. Alternatively, if a test has failed for you, mark that section with {X} and your nick. Even if someone has tested a section doesn't mean your can't or shouldn't repeat the test on your computer. Please try to complete all tests/sections you possibly can, and add your results to the chart. If you encounter any issues, or want to leave comments about something please add ** next to your nick, and explain your comment in the 'Additional Notes' section below the chart.

Installation Tests

	Ubuntu	Debian	Fedora	Arch Linux	openSUSE	RHEL	CentOS	Foresight	Mint
-u USERNAME	(./) swoody,
-t TEAMNUMBER	(./) swoody,
amd64)
-c 1
-k PASSKEY	(./) swoody,
normal|big)	(./) swoody,
-H host -P port
-u -t -k -b	(./) swoody,

Feature Tests

	Ubuntu	Debian	Fedora	Arch Linux	openSUSE	RHEL	CentOS	Foresight	Mint
name -u USERNAME	{X} swoody
name -t TEAMNUMBER	{X} swoody
archive
restore
monitor	(./) swoody,
status	(./) swoody,
proxy -p PORT -h HOST
start	(./) swoody**,
stop	(./) swoody**,
version	(./) swoody,
help	(./) swoody,

Network Management Tests

	Ubuntu	Debian	Fedora	Arch Linux	openSUSE	RHEL	CentOS	Foresight	Mint
deploy
network-archive
network-restore
network-monitor
network-status
network-name
network-start
network-stop
armageddon

Additional Notes

swoody

• 'sudo origami stop/start' works, but does not return me to a command prompt
• 'sudo origami stop' runs the "Sending 'End_your_work' signal" twice (to different PID's), taking 10 seconds to shutdown, rather than 5 seconds