"Fossies" - the Fresh Open Source Software Archive

Member "node-runner-0.6.0/INSTALL" (29 Dec 2004, 6631 Bytes) of package /linux/www/old/node-runner-0.6.0.tar.gz:


As a special service "Fossies" has tried to format the requested text file into HTML format (style: standard) with prefixed line numbers. Alternatively you can here view or download the uninterpreted source code file.

    1 Here's the easy way...
    2 
    3 Automatic Installation Instructions
    4 ===================================
    5 
    6 1. Unzip the compressed node-runner-0.6.x.tar.gz.
    7 
    8    # tar -xzf node-runner-0.6.x.tar.gz -C /where/ever
    9 
   10 2. For NEW installs, create the database for Node Runner
   11    if you haven't done so already.
   12 
   13    /location/of/mysql/bin/mysql -uroot -p
   14 
   15    mysql> create database <nameofyourdatabase>;
   16 
   17    mysql> GRANT CREATE,INSERT,UPDATE,DELETE,SELECT,ALTER,DROP \
   18        -> ON <nameofyourdatabase>.* TO <username>@localhost \
   19        -> IDENTIFIED BY '<password>';
   20 
   21    mysql> quit;
   22 
   23 3. Run the install script using your PHP (CLI) interpreter,
   24    and follow the instructions.
   25 
   26    # cd /where/ever/you/extracted/the/tar/file
   27    # /path/to/php -q installer.php
   28 
   29 That's it.  Done.
   30 
   31 
   32 
   33 
   34 And for those who wish to do things the hard way...
   35 
   36 Manual Installation Instructions
   37 ================================
   38 
   39 1. Unzip the compressed node-runner-0.6.x.tar.gz.
   40 
   41    # tar -xzf node-runner-0.6.x.tar.gz -C /where/ever
   42 
   43 2. Create a directory under your default web documents directory
   44    to hold the Node Runner web interface files.  If you are upgrading
   45    from a previous version, a similar directory should already exist.
   46    Note that this does not need to be on the same machine that the
   47    Node Runner query script (node.start) will run.
   48    (Ex. Apache - /usr/local/httpd/htdocs/node-runner/)
   49 
   50 3. Copy the contents of the html directory to this newly created
   51    directory in your web documents directory.
   52 
   53 4. Open the 'connect.php' file with a text editor, and modify the
   54    location of the $etcdir variable.  This should reflect the final
   55    location of the "etc" directory on the machine.
   56 
   57 5. Copy the rest of the files/directories from the installation to
   58    the directory of your choice. (Ex. /usr/local/node-runner/)
   59 
   60 6. In the "etc" directory, modify the appropriate information in the
   61    'nr.inc' file.  All fields should are explained with comments.
   62    (You may choose to leave the database username and password blank
   63    until the database is setup in Step 7.)
   64 
   65 7. You now need to set up the database for use with Node Runner.
   66    If you are upgrading your version of Node Runner, skip to step 8.
   67    (These instructions assume you are using MySQL.)
   68 
   69    /location/of/mysql/bin/mysql -uroot -p
   70 
   71    mysql> create database <nameofyourdatabase>;
   72 
   73    mysql> GRANT CREATE,INSERT,UPDATE,DELETE,SELECT,ALTER,DROP \
   74        -> ON <nameofyourdatabase>.* TO <username>@localhost \
   75        -> IDENTIFIED BY '<password>';
   76 
   77    mysql> quit;
   78    
   79 8. The sql file for version 0.6.0 attempts to DROP one of the database
   80    tables because it is no longer needed by the program.  The INSTALL docs
   81    for previous versions did not specify that the database user for Node
   82    Runner needed the DROP permission, so you will either need to change
   83    the database user permissions (see step 7 above), or log into the
   84    database as root and DROP the database manually.  For the latter, open
   85    the appropriate .sql file for this version and execute any DROP statements.
   86    Or, you could just leave it, since the table should be empty anyway.
   87 
   88 9. Next, the tables need to be imported for use with the database
   89    that was just created.  You will need to modify the database variables
   90    in the 'sql/nr-mysql-setup.php' sql file, then execute it like this:
   91 
   92    # /path/to/php -q sql/nr-mysql-setup.php
   93 
   94    Or, if you are upgrading from a previous version of Node Runner,
   95    you should use this step with the appropriate upgrade file.  Remember
   96    that you will need to modify the database variables in each .php file
   97    before executing the scripts.
   98 
   99    # /path/to/php -q sql/update-nr-to-v0.6.x.php
  100 
  101    PLEASE READ THE FOLLOWING NOTE!!!
  102    NOTE: The default port listed for the "Node Runner" (localhost) node in
  103          nr-mysql-setup.php (bottom) is 80.  This should be set for a port that
  104          is open on the local machine.  For example, if you use firewall
  105          software to block tcp port 80, or you are running this on a standalone
  106          machine without a web server, Node Runner will likely fail, because
  107          the last dependency (parent) it checks is itself.  If it cannot query
  108          itself on the selected port (80, for instance), the php script will
  109          loop endlessly until it crashes.  I REPEAT, IF THE node.start SCRIPT
  110          CANNOT QUERY THE MACHINE IT'S RUNNING ON, IT WILL FAIL!  I can't begin
  111          to describe the number of emails I've gotten over the years from people
  112          who fail to read and understand this documentation before reporting
  113          trouble with the program.  Anyway, a port scan of the localhost
  114          should provide you with a list of open ports to choose from when
  115          making this decision.  If your port scanner shows a port open, then
  116          the node.start script shouldn't have a problem querying that same port.
  117 
  118 10. The 'node.start' script is intended to be executed as a cron job,
  119     allowing for the customization of schedules.  Unfortunately,
  120     there is no way to run a PHP script as a daemon, so this is the
  121     best method I've found to get the job done.
  122 
  123     # crontab -e
  124 
  125     Insert a line similar to:
  126     0,2...58 * * * * /path/to/php -q /path/to/nr/node.start >> /tmp/nr-debug.txt
  127 
  128     And save the changes.  This will create a cron job that executes
  129     every 2 minutes to query servers.  If you are not familiar with
  130     the format of cron jobs, do your homework, then  see the README
  131     file for more information on cron scheduling and intervals for
  132     querying nodes.
  133 
  134     The trailing ">> /tmp/nr-debug.txt" is only necessary if you need
  135     to debug the output of the node.start script.  It does not harm
  136     anything to add it, and output is only generated to the file if
  137     the $debug option (nr.inc) is set to 1.
  138     
  139 11. Depending on how you have arranged your Node Runner files to this point,
  140     you may need to change the $path_to_etc variable in the first few lines
  141     of the node.start script.  It defaults to "etc/", so if you haven't moved
  142     your etc directory from it's original tarball location (relative to the
  143     node.start script), you should be okay.
  144 
  145 12. You will need to log in to the web interface after copying the
  146     contents of the 'html' directory to the appropriate location.
  147     To login, use 'admin' as a user, and 'node-runner' as the password,
  148     and remember to change it upon successful login.  Once logged in,
  149     you can also add users without administrative privileges.  These
  150     users will be able to view some settings and print reports, but will
  151     not have the privileges to change anything besides their own password.
  152