Some further (english-speaking ;-)) hints on experiment distribution.

git-svn-id: https://www4.informatik.uni-erlangen.de/i4svn/danceos/trunk/devel/fail@1062 8c4709b5-6ec9-48aa-a5cd-a96041d1645a
This commit is contained in:
adrian
2012-04-12 14:52:28 +00:00
parent 158146dcac
commit cbd8781538

View File

@ -317,10 +317,16 @@ themselves, they contain some documentation):
starts several instances of client.sh in a tmux session starts several instances of client.sh in a tmux session
- client.sh -- (Repeatedly) runs a single FailBochs instance - client.sh -- (Repeatedly) runs a single FailBochs instance
Some useful things to note:
TODO: ---------------------------
- bochs-distribution problematik - Using the distribute-experiment.sh script causes the local bochs binary to
- Ausgabenproblematik be copied to the hosts. If the binary is not present in the current directory
- in wiedeholten verteilten experimenten (nicht lokal) sollte man daran denken the default bochs binary (-> which bochs) will be used. If you have modified
dass der server nicht läuft bzw. funktioniert, wenn es noch eine existierende some of your experiment code (id est, your bochs binary will change), don't
coolcampaign.csv gibt forget to delete the local bochs binary in order to distribute the *new* binary.
- The runcampaign.sh script prints some status information about the clients
recently started. In addition, there will be a few error messages concerning
ssh, tmux and so on. They can be ignored for now.
- The runcampaign.sh script starts the coolchecksum-server. Note that the server
instance will terminate immediatly (without notice), if there is still an
existing coolcampaign.csv file.