UNIX only. Manage patches in LSF cluster.
Synopsispatchinstall [-f env_file] [--silent] package ...
Permission that is required to run this command depends on the package contents and the original cluster installation account. You normally log on as root to run the patchinstall command, but you can patch some binary files as cluster administrator (lsfadmin).
By default, the command installs one or more packages in an existing cluster.
The cluster location is normally determined by your environment setting, so ensure that your environment is set before you run this command (for example, you sourced the cshrc.lsf or profile.lsf file).
Specify the packages that you want to install.
The installer does some checking first. If it does not find a problem, it prompts you to proceed with installation. If you confirm, it backs up the current binary files to the patch backup directory and then installs the specified packages on the cluster, updating or adding new binary files. It does not modify any existing configuration files. If the installation of a package has problems, it automatically rolls back to the cluster’s previous state. It records the changes in the patch history directory. This additional checking can take more time than installing with lsfinstall.
- Do the checking for the packages without installing them. For more information, see the -c option.
- Roll back
- Remove the most recent patch and return the cluster to the previous patch level. To roll back multiple versions, you must roll back one patch level at a time, in the reverse order of installation. For more information, see the -r option.
If you want to enable installation through AFS, take the following steps.
- Modify patchinstall to set the environment. For the following original settings:
CHOWN="chown" CHMOD="chmod" IGNORECHECKFILEOWNER="n"Set the following environment:
CHOWN="asudo chown" CHMOD="asudo chmod" IGNORECHECKFILEOWNER="y"
- Create an environment file where all LSF paths point to the volrw instead of volro.
- Run the following
patchinstall -f environment_file package
The path to environment_file must include the correct LSF_TOPDIR installation directory.
- Check as if to install, but do not proceed with installation.
Specify each package that you want to check. You can specify multiple packages.
Checks that the existing cluster is compatible with the patch (the same version of the product is already installed on the same binary types). Fixes and fix packs might also require installation of a specific enhancement pack.
Checks that your user account has permission to write to the installation directory, backup directory, and history directory.
Lists existing files that are overwritten by the patch.
Lists files that to be added by the patch.
- -f env_file
- Use This option only if you cannot set your environment (for example, you cannot source
cshrc.lsf or profile.lsf).
Specify the full path and file name of a file (such as your LSF install.config file) that properly defines the parameter LSF_TOP.
If you use this option, the command gets the cluster location from this file, not from the settings in your environment.
- Outputs command usage and exits.
- Rollback. You must specify the most recently installed patch. The installer checks all binary
types and finds all instances where the most recently installed patch has the same build number.
These packages are removed and the cluster reverts to the previous patch level.
Specify the build number of the most recent patch or specify full path to the package you used to install the most recent patch. The installer automatically checks the package to determine the build. You cannot specify any other build.
To remove multiple patches and roll back multiple versions, you must run the command multiple times and roll back one patch level at a time.
You cannot roll back if the backup files from the previous patch level are unavailable (if you deleted them from the patch backup directory).
- Silent mode. Install or roll back without any interactive prompts for confirmation.
Status information and prompts are displayed in your command console.
When you patch or roll back the cluster, status information is logged to the patch.log file. When you check a package, status information is logged to the precheck.log file.
If any problems are found when you check a package, errors are displayed in your command console and also logged to the patch.err file.