IMPORTANT:

 - All client machines must have access to a common network share on a
   central server (NFS, SMB). The pathname can be different on each client.
   
   We will call the pathname to this share "renderd_path".
   
 - Only one network render job can be active at any given time
 
   

HOW TO:

 - Run iblender2 -D renderd_path on all client machines
   (no GUI will be brought up)
 
 - In the user preferences on the workstation that is used to
   initiate the network job, be sure the Renderd Dir (Renderd:)
   userpref is ALSO set to point to renderd_path.
   
   Remember to include a trailing slash

 - In the scene you want to render, activate the "Render Daemon"
   toggle
   
 - Specify the Output format. THIS MUST BE AN IMAGE FORMAT, not
   a movie format!

 - Press "ANIM"
 
 - After a while, check the "0 host(s) registered" popup. It should
   contain all hostnames of the clients you brought up.
   
 - You should see updates showing the current frame that is being 
   rendered on the network
   
 - The file "log" in the renderd directory will contain detailed
   information about the process
   
 - THE OUTPUT IMAGES will be placed in renderd_path/filename.blend/
   The "Output" setting will be ignored for network jobs so that
   clients having different pathnames for common shares can still
   be used to render.
 
 - Press "Cancel" at any time to cancel the job globally. All client
   machines will terminate this job and wait for new jobs.
   

BENEFITS:

 - No restarting of blender instances on client machines ever takes place.
   Thus this is the fastest network renderer available to date for Blender,
   as it never reloads the binary, and can handle static Envmaps.

 - Easy to set up and to use. It probably can't get much easier :)

 - Additional clients can 'punch in' at any time and will pick up the 
   currently running render job
   

CAVEATS:

 - Softbodies have to be baked because each frame depends on the previous
   frame if they're simulated in "real time"
 
 - DOF doesn't work with "Focus Lag" because each frame depends on the
   previous frame