This is RenderMan 21 Documentation you are viewing. The Rmanwiki home page will redirect you to the current documentation.

Page tree


The engine maintains the central job queue and assigns tasks to servers on the farm. It is also the central clearinghouse for status information reported from the blades. The engine also delivers the web content required by the Tractor Dashboard.Usage:tractor-engine [options]


--versionPrint version information, and exit.
-h, --helpPrint usage summary, and exit.
or -c path
Specify the directory containing tractor configuration files, default is /var/spool/tractor/config. Tractor-engine also checks for the environment variable TRACTOR_CONFIG as well.
--log=filenameSpecifies the 'filename' used for logging the engine's own diagnostics. Default is stderr.
--verbose or -vIncrease logging level to from NOTICE to INFO.
--quiet   or -qDecrease logging level from NOTICE to SEVERE.
--debugIncrease logging level to DEBUG.
--traceIncrease logging level to TRACE.
--httpdebugLog inbound http requests
or -n nnn
Set the number of thread created to handle i/o (default=ncores).
or -D nnn
Restrict concurrent dispatches (and license use).
--port=nSpecify the engine's inbound connection port (default=80).
--port=addr:portRestrict the inbound listener port to the network interface given by address - using port number port. By default the engine will listen for connections on port 80, on all interfaces. Example usage: --port=8080 or --port=
Allows a newly started engine process to gracefully take over from a still-running previous engine. The new engine sends a "drain and exit" message to the old engine, then waits for the old one to exit before proceeding to become the new engine service. In drain mode, the old engine stops assigning new work to requesting blades, and then exits when all previously launched tasks are complete. Partially complete jobs will remain in the queue and will continue being processed when the new engine takes over.
--pausedCauses a newly restarted engine to immediately enter the "pause all dispatching" state. Hence no new commands will be assigned to blades until an administrator manually re-enables dispatching using the red "play" button on the Dashboard's "Gears->Admin" tab. Even when the engine restarts in --paused mode, any existing commands that are marked as still-active in the job database will still be considered active by the new engine. In those cases, the still-running blades and the new engine will communicate to sort out which of those commands are actually still running.
--startupdelay=n  Engine simply sleeps for n seconds at startup.
--daemonEngine auto-backgrounds in system service mode.
--pidfile=filenameIn daemon mode, write final PID to filename.
--sigdfl=1Do not override default SEGV/BUS handlers.