BOINC_scriptgenerator

#!/bin/bash
# This script assumes that your username is boinc. Feel free to use ~/ or replace it with your current/desired username.
# Initiate two counter files:
echo 0 > /home/boinc/counter
echo 0 > /home/boinc/counter2
# Create one directory to contain all the boinc datadirs, for cleanliness:
mkdir /home/boinc/datafiles
# Create a password which you will use for remote administration:
echo "mypassword" > /home/boinc/datafiles/gui_rpc_auth.cfg
# Allow the IP from which you will have access to these machines:
echo "ip_of_the_machine_running_BoincTasks" > /home/boinc/datafiles/remote_hosts.cfg
# If you want access from more than one computer, uncomment the second line and copy it (not the one above!):
#echo "ip_of_the_second_machine_running_BoincTasks" >> /home/boinc/datafiles/remote_hosts.cfg
# Create the scripts which we will later use:
echo "#!/bin/bash" > /home/boinc/client_run.sh
echo "#!/bin/bash" > /home/boinc/project_attach.sh
echo "#!/bin/bash" > /home/boinc/project_update.sh
# Each running instance will need a different port. That is one of the reasons for the counter. However, since ports 1-1024 are reserved and we often have other ports bound to specific software, this will allow you to set a starting port for the running clients in order to avoid conflicts:
portIncrement=30000
# Create a simple loop which will iterate for as many times as the number of clients you want running (in this case 240):
while [ `cat /home/boinc/counter` -lt 240 ]; do {
        # First, read the counter:
        counter=`cat /home/boinc/counter`
        # The first client is 1, so we add 1 to the counter:
        let countNew=$counter+1
        # Create a variable which will take the port and offset it with the value of the variable we declared above:
        let port=$countNew+$portIncrement
        # Create the datadir for the current client (this will result in boincdata1, boincdata2 ...). I choose to name the folder zdatadirs so it shows last when I ls the contents of the folder.
        mkdir /home/boinc/zdatadirs/boincdata$countNew
        # Copy the authentication and host whitelist files into the newly created directory:
        cp /home/boinc/datafiles/gui_rpc_auth.cfg /home/boinc/zdatadirs/boincdata$countNew/
        cp /home/boinc/datafiles/remote_hosts.cfg /home/boinc/zdatadirs/boincdata$countNew/
        # Create the run command for this specific instance. The example shows the command line I use:
        echo "boinc --allow_multiple_clients --allow_remote_gui_rpc --gui_rpc_port $port --daemon --dir /home/boinc/zdatadirs/boincdata$countNew --no_gpus --suppress_net_info" >> /home/boinc/client_run.sh
        # Add some dialogue so you are aware what's happening once you run the client_run script:
        echo "echo Started client $countNew/240. Sleeping for 0 seconds..." >> /home/boinc/client_run.sh
        # If you want to start the clients gently, uncomment the following line and modify the echo above to reflect the delay (in seconds) between launching of the instances:
        #echo "sleep 3" >> /home/boinc/client_run.sh
        # Otherwise, a delay of 0 works fine.
        # Create the script which will connect to each running client via boinccmd and attach it to a certain project:
        echo "boinccmd --host the_machine_or_VMs_IP:$port --passwd mypassword --project_attach http://url.of.the.proj.ect/ FULL_CONTROL_PASSKEY" >> /home/boinc/project_attach.sh
        # Create a dialogue. I recommend adding a delay here because the burst in open connections and network communications can cause the server to reject you for some time, or, well, bring your router down. :)
        echo "echo Attached $countNew/240 to project. Sleeping for 15 seconds..." >> /home/boinc/project_attach.sh
        echo "sleep 15" >> /home/boinc/project_attach.sh
        # Now, this xmlconfig contains all the XML data you need to add to your BoincTasks's computers.xml file in order to see them. This is a workaround for having to add every single one manually. I recommend connecting to one client with the same password you've chosen in order to see it parsed, then paste the string below. Otherwise you will not be able to connect to your clients. The id_name tag defines how the computer will be seen in your BoincTasks window, so pick any name you wish.
        cat <<EOF >> /home/boinc/xmlconfig
<computer>
    <id_name>BOINC240-$countNew</id_name>
    <id_group></id_group>
    <ip>`hostname -I`</ip>
    <mac></mac>
    <checked>1</checked>
    <port>$port</port>
    <password>%-something%-%something%%-%something-1</password>
</computer>
EOF
# Update the counter, and close the loop.
echo $countNew > /home/boinc/counter
}
done
#>>>>>ADDING PROJECT_UPDATE<<<<<
# Now we use the second counter which will allow us to run two scripts at the same time (project_attach and project_update):
while [ `cat /home/boinc/counter2` -lt 240 ]; do {
count2=`cat /home/boinc/counter2`
let count2New=$count2+1
let port2=$count2New+$portIncrement
cat <<EOF >> /home/boinc/project_update.sh
boinccmd --host the_machine_or_VMs_IP:$port2 --passwd mypassword --project http://url.of.the.proj.ect/ update
echo "Updated project on client $count2New/240. Sleeping for 15 seconds..."
sleep 15
EOF
echo $count2New > /home/boinc/counter2
}
done
#>>>>>END OF PROJECT_UPDATE<<<<<

# Finally, mark our newly created scripts as executable:
chmod +x /home/boinc/client_run.sh
chmod +x /home/boinc/project_attach.sh
chmod +x /home/boinc/project_update.sh

# If you want to automatically create all these scripts AND run them (simultaneously, in the total timespan of 3630s /1h, 0m, 30s/), uncomment the following lines:
#echo "Running scripts..."
sh /home/boinc/client_run.sh
sleep 10
echo "Attaching projects in the background..."
sh /home/boinc/project_attach.sh &
sleep 30
echo "Now starting to update the projects... This runs with a 30 seconds delay from the attached clients."
sh /home/boinc/project_update.sh