Purify
Introduction / Philosophy
Installation of Purify under /software is straighforward. You are referred
to the installation documentation. This page details only some points of
which to be aware.
Purify has a 10000 user license, and as such is installed on several
/software servers without regard to tallying of licenses.
Symbolic links to the actual executables should be made on the corresponding
/usr/server servers in order to add the real Purify path to users' PATHs
without. This is important since VLT users already have a PATH that
is very long, and lengthening it will break the shell (word too long).
The software is installed in a read-only environment (/software and
/usr/server is mounted read-only). The installation documentation is a
little unclear on the repercussions of this. But it comes down to the following
two points.
Firstly a symbolic link for redirecting the cache off the read-only
filesystem must be put into the installation directory. The link redirects
to /var/tmp/pure-cache and it is then up to each NFS client as to
whether this is further redirected to where more space is available or
whether it is a real directory.
The license system expects to be able to write information to a file
as each user starts up a purify product. Fortunately, if the software cannot
do this, then it writes (unsharable and therefore useless) license
usage info into a dot file in the user's home directory.
$Header: /home/ct/serco/ahuxley/docs/html/serco-faq/new/software/applications/RCS/purify.html,v 1.3 1997/08/14 10:02:19 ahuxley Exp ahuxley $