Page tree

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

 

Code Block
themeConfluence
sudo /opt/pixar/RenderMan-Installer/bin/RenderManInstaller

 

The installer will connect with the RenderMan Pixar Server and download your licensed components. During the installation process you will see that the default location for installation is /opt/pixar This will become the root directory for all of the software components listed above.


Carousel Image Slider
infinitefalse
sliderHeight350
labelsFilterinstallerLinux
slidesToScroll2
slidesToShow2

Expand
titleClick here to expand manual installation instructions...

Command Line Installation

If you are not using the .rpm method above, the software can also be installed via command line using a terminal window. You must obtain the .pkg files using your forum login.

 

Installing to the default location

To install the software to the default location, first change to the directory where the .pkg files are located, and from a root shell type:

Code Block
themeConfluence
> installer -pkg RenderManProServer-version-linuxflavor.pkg -target /

For example:

Code Block
themeConfluence
> installer -pkg RenderManProServer-Installer-21.0_1590950-linuxRHEL6_gcc44icc150.x86_64.pkg -target /

 

Installing to a drive other than /

To install the packages to a different drive, the / target of the default path can be replaced. For example, to install to a second disk/Volumes/HD2/, from a root shell type:

Code Block
themeConfluence
> installer -pkg RenderManProServer-21.0_1590950-linuxRHEL6_gcc44icc150.x86_64.pkg -target /Volumes/HD2

Setting Up the User's Environment

Environment Variables

There are several environment variables that users should set. These can be added to your .cshrc, .tcshrc (or other startup) file, like so:

setenv RMANTREE /opt/pixar/RenderManProServer-21.0

or, if you are using bash:

export RMANTREE=/opt/pixar/RenderManProServer-21.0

The following environment variables are recommended:

  • RMANTREE - establishes the location of your PRMan distribution.
  • RMANFB - establishes your framebuffer display program.
  • path - establishes the searchpath for the execution of programs, this probably already exists, so it is just a matter of adding $RMANTREE/bin to your path.
  • RDIR - specifies a directory where additional configuration files can be found, e.g. a site-specific rendermn.ini file.

 

Systems administrators may also choose to use the PIXAR_LICENSE_FILE variable to point to their software license, in lieu of using the defaults, or may point to an arbitrary location for their license via the /licenseserver preference in their own custom, site-specific .inifiles, and absolutely should not add that preference to a factory-shipped .ini.

 

If you wish to use a location other than the default for your pixar.license file, you can optionally set a PIXAR_LICENSE_FILE environment variable to point to an arbitrary location.

 

Note

We highly recommend that, rather than editing the rendermn.ini file in your installation directory ($RMANTREE/etc), you create a duplicate file containing your site-specific overrides and place it in a separate directory, referenced via an $RDIR environment variable.


Python

If you plan to take advantage of the Python binding you will need to download Python installer from www.python.org. RenderMan Pro Server 21 binding is compatible with 2.7, 3.4, or 3.5.

Help

If you require further assistance, please check out the RenderMan Support Forum. Note that registration is required.

...