// THIS SYSTEM IS NOT SUPPORTED BY BOINC. USE AT YOUR OWN RISK // // This directory contains a system that allows // users to submit jobs to a BOINC project. // // Major revisions may be required to make this work // (and to make it secure) on your project. // Please read and understand all the code before using it. // // Contributed by Dr. M.F. Somers, Leiden University // // BASIC INSTALL: // // 1) add tables to database using create_queue.sql: // // mysql yourprojectdb < create_queue.sql // // 2) copy files into html directory of your project so // apache will server them: // // cp inc/* ~/Classical/html/inc (beware the user.inc might be overwritten, use diff!) // cp user/* ~/Classical/html/user // cp ops/* ~/Classical/html/ops // // 3) Make sure you have defined the following tags in your config.xml: // // // // // // // // // // 4) Make sure you have a WU and a result template in the template directory // for each application with the names similar to 'queue_uppercase_work_unit_template' // and 'queue_uppercase_result_unit_template'. These will be used to invoke 'make_work'. // // That shoult be it; now the queue has been setup and by default allows users to have 5 // jobslots per application. If your do not want users to be able to submit to an application // make sure you list that app (it's ID) into the new q_restricted_apps table. The new // q_users table can be used to allow users access to restricted apps or set different // limits that the default 5 jobslots. The new q_list table is the list of allw WU's that // have been submitted through the queue code... // // questions? send me a mail at m.somers@chem.leidenuniv.nl // // Example work unit template: // // // 0 // // // // // 0 // classical.in // // // classical.in classical.out classical.stdout // 2 // 2 // 16 // 16 // 8 // 43200 // // // // Example result template: // // // // 536870912 // // // // // // // // // 536870912 // // // // // // // // // // classical.out // // // // classical.stdout // // // //