[Debian Wiki] Update of "BOINC/ServerGuide" by SteffenMoeller

[Debian Wiki]

Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Debian Wiki" for change notification.

The "BOINC/ServerGuide" page has been changed by SteffenMoeller:
http://wiki.debian.org/BOINC/ServerGuide?action=diff&rev1=71&rev2=72

Comment:
Bringing startup back to main ServerGuide, rearrangement

  
  = Add functionality =
  
+ This section brings your BOINC project to life. 
+ 
+ == Setting up BOINC's Example Application ''upper_case'' ==
+ 
  This section is currently been brought to some better shape at [[BOINC/ServerGuide/AppDeployment]].
  
- == Configure and start BOINC demons ==
+ == Add your own application ==
  
+ The only thing that counts to have is the application that helps your very personal task at hand. This will be addressed in the upcoming section. The section at hand will take one of the example projects.
- Please stay in that project directory and just use the default configuration
- as a start.
  
+ ||<style="background-color: red; width: 50%; vertical-align:top">Previously||<style="background-color: lightgreen; width: 50%; vertical-align:top;">Now||
+ ||<style="vertical-align:top; text-align: left"><<Include(BOINC/ServerGuide/Include/PreparationWrapperOld)>>||<style="vertical-align:top; text-align: left"><<Include(BOINC/ServerGuide/Include/PreparationWrapperNew)>>||
+ ||[[BOINC/ServerGuide/Include/PreparationWrapperOld|source]]||[[BOINC/ServerGuide/Include/PreparationWrapperNew|source]]||
+ 
+ 
+ == Start BOINC demons ==
+ 
+ Now its time to start the project, assuming we are still inside the project root,
+ 
+ {{{
+ $./bin/start
-  1. Read information from file 'project.xml' and put into the database {{{
- sudo bin/xadd
- }}} The tool [[http://boinc.berkeley.edu/trac/wiki/XaddTool|xadd]] configures the project by parsing the 'project.xml' file. That 'project.xml' file initially only lists the most common platforms. Then it mentions the application that should be supported, which is 'uppercase'.
-  1. add the binary to be distributed to the clients. For the applications in 'project.xml', a folder in the 'apps' directory must be created and the respective binary be placed into that.{{{
- to be written, this is just guesswork for the very moment.
- sudo mkdir apps/uppercase
- sudo chown root:boincadm apps/uppercase
- sudo chmod 770 apps/uppercase
- # works for the Debian boinc-server package:
- sudo cp /usr/lib/boinc-server/apps/upper_case apps/uppercase/uppercase_$(arch)-pc-linux-gnu
- # copy it from your source directory if not running that package
- }}} The $(arch) identifies the platform that this installation is performed on and consequently that the binary in /usr/lib/boinc-server is compiled for. The information on the availability of that binary needs to be communicated to the database by executing the [[http://boinc.berkeley.edu/trac/wiki/UpdateVersions|update_versions]] tool by a mere {{{
- sudo PYTHONPATH=/usr/share/boinc-server/py bin/update_versions
- }}}.
-  1. start the demons {{{
- sudo bin/start
- }}} Running [[http://boinc.berkeley.edu/trac/wiki/StartTool|start]], this should show something like {{{
- Entering ENABLED mode
+ Staying in ENABLED mode
  Starting daemons
    Starting daemon: feeder -d 3
    Starting daemon: transitioner -d 3
    Starting daemon: file_deleter -d 3
+ }}}
- }}} and after some academic minute the shell prompt should return. The UNIX tool {{{top}}} should just show your regular BOINC work units (assuming that your server remains a good client until it is busy). A "ps aux | tail -20" should list something like {{{
- root      4551  0.4  2.1  46864 21776 ?        S    10:33   0:00 feeder -d 3
- root      4553  0.0  0.2  35312  3004 ?        S    10:33   0:00 transitioner -d 3
- root      4555  0.0  0.2  27336  2240 ?        S    10:33   0:00 file_deleter -d 3
- }}} Something lets me think that those processes should better run as "boincadm" than via 'sudo', but, well, let's be happy for now.
  
- == Add your own application ==
+ And ''./bin/status'' can be used to check status of the project.
+ {{{
+ $ ./bin/status
+ BOINC is ENABLED
  
- The only thing that counts to have is the application that helps your very personal task at hand. This will be addressed in the upcoming section. The section at hand will take one of the example projects.
+ DAEMON  pid  status      lockfile disabled  commandline
+    1  16574  running     locked   no        feeder -d 3
+    2  16576  running     locked   no        transitioner -d 3
+    3  16579  running     locked   no        file_deleter -d 3
  
- ||<style="background-color: red; width: 50%; vertical-align:top">Previously||<style="background-color: lightgreen; width: 50%; vertical-align:top;">Now||
- ||<style="vertical-align:top; text-align: left"><<Include(BOINC/ServerGuide/Include/PreparationWrapperOld)>>||<style="vertical-align:top; text-align: left"><<Include(BOINC/ServerGuide/Include/PreparationWrapperNew)>>||
- ||[[BOINC/ServerGuide/Include/PreparationWrapperOld|source]]||[[BOINC/ServerGuide/Include/PreparationWrapperNew|source]]||
+ TASK last run period    next run lock file disabled commandline
+    1    ?     24 hours     NOW   unlocked  yes       db_dump -d 2 -dump_spec ../db_dump_spec.xml
+    2    ?     1 days       NOW   unlocked  yes       run_in_ops ./update_uotd.php
+    3    ?     1 hour       NOW   unlocked  yes       run_in_ops ./update_forum_activities.php
+    4    ?     7 days       NOW   unlocked  yes       update_stats -update_users -update_teams -update_hosts
+    5    ?     24 hours     NOW   unlocked  yes       run_in_ops ./update_profile_pages.php
+    6    ?     24 hours     NOW   unlocked  yes       run_in_ops ./team_import.php
+    7    ?     24 hours     NOW   unlocked  yes       run_in_ops ./notify.php
+ }}}
  
  == Config clients ==