skynet

Path: bin/skynet
Last Update: Wed May 28 14:35:19 -0700 2008

This is the main skynet starter script. It can be used to start the skynet_tuplespace_server as well as all skynet workers. It is important that this script has access to your code. If you want to run skynet within your code you‘ll want to read about bin/skynet_install

Usage: skynet [options]

    -w, --workers WORKERS            Number of workers to start.  The default is 4 and is stored in Skynet::CONFIG[:NUMBER_OF_WORKERS]
    -i, --increment-worker-version   Increment Worker Version
    -a, --add-workers WORKERS        Number of workers to add.
    -k, --remove-workers WORKERS     Number of workers to remove.
    -r, --required LIBRARY           Require the specified libraries
        --restart-all-workers        Restart All Workers
        --restart-workers            Restart Workers

If you have chosen to use the TupleSpace message queue adapter this script will see if there is an available TS first and start one if there is not. You can also start the bin/skynet_tuplespace_server manually.

Running skynet starts a Skynet::Manager which in turn spawns the Skynet::Worker processes with the appropriate options. You only need to run skynet once per machine. If you want to add more workers, use the appropriate flags above to do so. Only one manager should be running per machine. The Skynet::Manager does not dole out tasks

You should set all of your Skynet::CONFIG (or Skynet.configure()) options here (or in one of your environment files.) See Skynet::Config for more information on configuration options.

Required files

rubygems  

[Validate]