Pixar
March, 1996
This document explains how to install the RenderMan Toolkit software for UNIX based computer systems. The distribution medium is a compact disk containing release files for five supported computer system architectures.
This release of the RenderMan Toolkit is supported on the following computer systems:
This distribution can be installed on any supported workstation with approximately 40 Mbytes of disk space. Also recommended are 32 Mbytes or more of system memory and a full color display.
The basic distribution comes as one compact disk (CD). Installation may be done with a CD that is local to the machine, or which is accessible via a network.
The top level directory of the CD contains a script, rinstall, which performs the software installation. The actual RenderMan Toolkit software distribution is contained on the CD in tar files. rinstall will select the proper tar files and extract the contents. The files contained in the tar file on the release tape are listed in Appendix A of this document.
The remainder of this document describes the procedure to follow in loading the RenderMan Toolkit software release onto a file system.
Throughout this document, commands you are expected to type are shown in a Bold Courier font, while information that is printed by the system is shown in Courier. Comments are typically shown to the right of a typed command in italics, and surrounded by parentheses. When command line operations are presented, the command interpreter's prompt is shown for reference; e.g.,
prompt% (our favorite prompt)
This section explains the procedure for installing the RenderMan Toolkit release software on your machine. The software is supplied on a single compact disk. The software is configured for installation in the directory /usr/local/prman. If it is placed elsewhere, a symbolic link to the software must be made for /usr/local/prman. (It is possible to set up the renderer to run from another path location. However, we advise that you test it from /usr/local/prman before trying this. See Section 2.6 of this manual and the PhotoRealistic RenderMan User's Manual for details on running the renderer from another path.)
The steps to perform in installing the RenderMan Toolkit release are:
Note that these procedures are needed only when a system is first installed; procedures for normal system operation are described in the PhotoRealistic RenderMan User's Manual.
The computer system should be configured with a current version of native Unix operating system. Compatibility between operating system releases is up to the computer system vendor. For reference, the 3.6 distribution has been built under these operating system releases:
The system should be equipped with an appropriate CDrom drive or have network access to a system with such a drive.
You should have a copy of the PhotoRealistic RenderMan encrypted license file information. This will be required for the installation of the Flexible License Manager which is used to control access to the renderer. The encrypted license file information maybe provided as a hardcopy document in the RenderMan Toolkit release package, a hardcopy faxed to you by Pixar or a file sent to you via electronic mail from Pixar.
The RenderMan Toolkit release as distributed is configured to support image output to:
In addition, Silicon Graphics specific window and file drivers are available in the SGI versions. See the document PhotoRealistic RenderMan Display Driver Guide for information on how to add other output drivers to the system.
Although root (or super-user) permissions may be required in order to create the installation directory, we recommend that the rest of the installation be performed under a user-id other than that of the root. Actually installing the software while logged in as root may leave the files with undesired ownership and permissions.
On a system with a local CDrom drive, the software can be loaded onto disk as follows:
prompt% mkdir /usr/local/prman (create installation directory)(prompt% is shown as the prompt from the command interpreter). (The mkdir may need to be done as superuser. If so, the ownership of the /usr/local/prman directory may need to be modified with the chown command.)
prompt% CDrom-directory/rinstall
Remember that if you extracted the software into a location other than /usr/local/prman, then you must create a symbolic link for /usr/local/prman that points to this location; e.g.
prompt% ln -s /extradisk/prman /usr/local/prman(Note that the symbolic link may have to be made as root depending on the permissions set for the /usr/local directory.)
If the installation target has no CD drive, the best approach is to place the distribution CDrom into a CD drive available on the network and use the Network File System (NFS) to enable the installation. One could export the CDrom file system to the target machine and run the rinstall script there. Alternately, one could use NFS to mount the target file system onto the computer system with the CD drive and run the rinstall script there.
PhotoRealistic RenderMan 3.6 is distributed for use in a network environment. The License Manager Software requires that one (or more) machines in your network operate as a license server. License servers regulate user requests for the software. A license file is provided when you receive PhotoRealistic RenderMan 3.6 that contains encrypted information detailing the machines authorized as license servers, the number of copies of PhotoRealistic RenderMan 3.6 that may be executing simultaneously and the expiration date of the license. The License Manager Software and license file must be properly installed in order for PhotoRealistic RenderMan 3.6 to function properly. The instructions in this section describe how to configure the License Manager Software.
If you are upgrading from PhotoRealistic RenderMan 3.5, your old license file will not work with PhotoRealistic RenderMan 3.6. You must install the new license file sent to you with PhotoRealistic RenderMan 3.6. The new license for release 3.6 can, however, be used by release 3.5 software. Note also that the License Manager Software that comes with PhotoRealistic RenderMan 3.6 should not be run on a single host simultaneously with the License Manager Software from previous releases.
Appendix B provides more complete information regarding the License Manager Software, including installing multiple server configurations, reserving copies of PhotoRealistic RenderMan 3.6 for individuals or machines, and obtaining statistics regarding requested usage patterns of PhotoRealistic RenderMan 3.6.
If you have existing applications installed on your network that employ the Flexible License Manager, you should skip the next two subsections and proceed directly to Section 2.3.3.
The configuration of the License Manager is provided by a license file, license.dat, that resides in the directory /usr/local/prman/etc. The license file will contain SERVER lines for each host designated as a license server.
Locate the PhotoRealistic RenderMan 3.6 encrypted license file information. You will need to edit the sample license file provided as part of the release (/usr/local/prman/etc/license.dat) replacing the existing information with your site-specific data provided by the encrypted license file information. The license file should normally be protected from write accesses to avoid accidental overwrites. Before editing the license file you must unprotect it by typing:
prompt% cd /usr/local/prman/etc prompt% chmod +w license.datBe sure to set the protection back when you are done:
prompt% chmod -w license.dat
The SERVER line should be replaced with the SERVER line(s) from the encrypted license file information, and the FEATURE line replaced with the new FEATURE line.
If you have a copy of the PhotoRealistic RenderMan encrypted license file information in machine-readable form, simply copy the file into /usr/local/prman/etc/license.dat.
You should now start a license server daemon. The license server daemon can be started on a host by using the script /usr/local/prman/etc/startlm.sh. The script may be invoked interactively by any user or from the system startup. The license manager needs no special privileges to run.
For most systems a file of the form:
#! /bin/sh
RMANTREE=/usr/local/prman ; export RMANTREE
# Start the license manager
case "$1" in
'start')
( cd ${RMANTREE}/etc ; ./startlm.sh) > /dev/null 2>&1
;;
'stop')
;;
*)
echo "usage: $0 {start|stop}"
;;
esac
can be placed into the directory:
/etc/rc2.d for SGI/SUN,
/sbin/rc2.d for DEC, using a file name such as
S99startlm..
For IBM systems, a command to execute the startup script can be placed into /etc/rc.net.
The license server daemon must be up and running on a majority of the license server hosts in order for the renderer to run.
If the machine is not connected to a network, be sure that the hostname from the SERVER line also appears in the /etc/hosts file on the same line with the localhost address of 127.0.0.1
It is possible that you have existing, previously installed applications that employ the Flexible License Manager. If so, you should already have a common license.dat file and you are probably already running a license manager daemon. If this is the case you should:
prompt% cd /usr/local/prman/etc prompt% mv license.dat license.dat.save
prompt% cp /usr/local/license.dat license.dat
To verify the installation procedure has been performed properly the setup confidence test should be run. This test renders a 128 by 96 image of a blue teapot with a matte surface and a logo texture-mapped onto the front. The calculated image is then compared against a precomputed version of the same image as a consistency test. Note that since floating point calculations vary between hardware environments, this comparison is usually not an exact comparison. Thus the comparison may be treated as successful even if there are differences between the images.
To run the confidence test do the following:
prompt% cd /usr/local/prman/prman/etc/setup prompt% makeIf everything goes well you will see the following printed out:
/usr/local/prman/prman/bin/shader finite.sl finite: /usr/local/prman/prman/bin/shader shield.sl shield: rm -f trial.tif cp /dev/null trial.tif; chmod 0666 trial.tif /usr/local/prman/prman/bin/render trial.rib cmptiff trial.tif check.tif The images are identical.If the comparison failed, the cmptiff program will print the following:
The images are significantly different in %d pixels out of %d.
In order to use the PhotoRealistic RenderMan software, users should add the following directory to their path environment variable: /usr/local/prman/bin.
To start the Network RenderMan server execute the following commands:
prompt% cd /usr/local/prman/etc prompt% nrmstart
The Network RenderMan server may be started interactively by any user. It can also be started automatically at system boot time in the same manner as the license manager startup, see section 2.3.2 above.
If for some reason it is important to install this software somewhere other than on /usr/local/prman, and a symbolic link is not sufficient, it can be installed on an arbitrary location and referenced using the RMANTREE environment variable. This might occur, for example, in upgrade situations, where both the previous release and this release need to be on-line simultaneously.
In this situation, set the environment variable RMANTREE to be the new location. For example (using the C shell):
prompt% setenv RMANTREE /usr/local/prman.3.6
Then all references to /usr/local/prman throughout this
manual and other manuals may be assumed to refer instead to the value
of RMANTREE.
All users of the software must similarly set their path variables and
the RMANTREE enviroment variable
(usually in their shell startup script, .login
for the C shell and .profile for the Bourne shell).
Refer to the PhotoRealistic RenderMan User's Manual for details
about running the PhotoRealistic RenderMan software.
PhotoRealistic RenderMan uses Globetrotter Software's Flexible License Manager® (FlexLM) to accomplish software protection in the Unix® environment. The software protection system regulates use according to the number of licenses available for simultaneous use and the expiration date of the licenses. Use can be further regulated by the system adminstrator to reserve licenses for specific users or specific computer systems.
The rendering system consults a license file and communicates with a license server to insure that the site has the proper license to run the software. The license server need not run on the same computer system as the renderer, as long as it can be reached through the network. To protect users from system crashes and downtime on the computer system running the license server, copies of the license server can be running on 3 computer systems. As long as a majority of the license servers remain running, users have access to the licensed software.
The FlexLM End User Manual provided by Globetrotter Software is provided in this package for reference. Some RenderMan Toolkit specific configuration details are: