
INSTALLATION INSTRUCTIONS FOR VRAY STANDALONE / X86 / LINUX
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

    Standard installation:
    ----------------------

	1. Our installs are in the form of a .zip file. You must first unzip 
	   it, e.g.:
	
		# unzip VRayStdInstall.zip
		
	2. The archive contains the installer binary, `installer'; 
	   run it as root.
	
		# ./installer
		
	3. Follow the instructions.


    Using V-Ray Standalone:
    -----------------------
    
	V-Ray binaries are located in the bin/x86/linux/ subdir of the
	installation root. For example, to run vraysl:
	
		# cd /usr/ChaosGroup/vray/standalone_for_x86/bin/x86/linux/
		# ./vraysl -scenefile=../../../scenes/cornell.vrscene

    Licensing:
    ----------
    
	V-Ray keeps its license info in $HOME/.ChaosGroup (e.g. 
	"/root/.ChaosGroup" for the "root" user).
	
	1. VRFLClient.ini: 
		This file keeps license information for the Standalone.
		The format is:
		
		
		[Network]
		Port=<server port>
		OnlineID=MD5SUM
		Server=<server host>
		
		
		
		Of course, you could generate/update this file, using 
		`setvrlserver'. See 4)
	
	2. VRFLServer.ini:
		This file keeps license info for the VRLServer.


	3. VRLServer:
		V-Ray License Server - this program permits licensing
		across a network connection. You should place VRLServer on one
		machine and run it there.
		
		NOTE: VRLServer requires GNOME (or, at least, GTK) installed.
		NOTE: VRLServer will ask for a license the first time it is
		started.
		
	4. setvrlserver:
		This is a small utility, which creates or modifies the 
		$HOME/.ChaosGroup/VRFLClient.ini file for you.
		
		For example, if you want the set the server host to
		192.168.1.10, issue:
		
		# ./setvrlserver -server="192.168.1.10"
		
		within bin/x86/linux

    Example licensing scenarios:
    ----------------------------
    
	Scenario A: just one workstation:
		1) You should have GNOME and GUI.
		2) Use vrlserver to create and store licensing info.
		3) Use vraysl to do renders. You don't need to have `vrlserver'
		   running for that - vraysl finds the license by itself.
		   
	Scenario B: Many render nodes:
		1) Let's assume we have three machines, A, B and C.
		2) A will be the vrlserver (could be used for rendering, too).
		   A should have GNOME and GUI. It will be running VRLServer.
		   
		3) B & C might not have GNOME or GUI. If you use -display=0
		   option on vraysl, you may operate the rendering under the
		   linux console.
		
		4) B & C need to be instructed to use A as a license server.
		   E.g. If A's IP address is 192.168.1.10, issue:
		   
		# ./setvrlserver -server="192.168.1.10"
		
		   on both B and C. In order to render, you will need to have
		   vrlserver running on A.

    Quick/Automatic installation:
    -----------------------------
   
	After a successfull installation, the linux installer writes a script
	file, called "installcfg.txt". It may be used later for automated
	installs.
	
	1) Installing when you have `installcfg.txt' locally:
	
		# ./installer -fromFile=<path to installcfg.txt>
		
	2) Installing when you have `installcfg.txt' on a HTTP or FTP server:
	
		# ./installer -fromFile="http://server-name.tld/path/to/installcfg.txt"
		
		NOTE: this requires GNU wget.
