Command Line Option
|
Function
|
system1 system2...
|
Specifies the systems on which to run the installation options. A system name is required for all options. If not specified, the command prompts for a system name.
|
-configure
|
Configures the product after installing using the
-installonly option.
|
-enckeyfile encryption_key_file
|
See the -responsefile and the -encrypt options.
|
-encrypt password
|
Encrypts password using the encryption key provided with the -enckeyfile option so that the encrypted password can be stored in response files.
|
-installpkgs
|
Displays all product packages in correct installation order. Output can be used to create scripts for command line installs, or for installations over a network. See the requiredpkgs option.
|
-installonly
|
Installs packages, but does not configure the product.
|
-keyfile ssh_key_file
|
Specifies a key file for secure shell (SSH) installs. This option passes -i ssh_key_file to every SSH invocation.
|
-license
|
Registers or updates product licenses on the specified systems.
|
-logpath log_path
|
Specifies a directory other than /opt/VRTS/install/logs as the location where installer log files, summary files, and response files are saved.
|
-noextrapkgs
|
Additional packages can be installed so that you can upgrade to another Symantec product simply by installing a new license. The -noextrapkgs option bypasses installation of extra product packages to simplify future maintenance updates.
|
-nolic
|
Allows installation of product packages without entering a license key. Licensed features cannot be configured, started, or used when this option is specified.
|
-nooptionalpkgs
|
Bypasses installation of optional product packages such as user documentation and manual pages.
|
-nostart
|
Bypasses startup of the product following installation and configuration.
|
-patchpath patch_path
|
Designates the path of a directory that contains all patches to install. The directory is typically an NFS-mounted location and must be accessible all specified installation systems.
|
-pkgpath package_path
|
Designates the path of a directory that contains all packages to install. The directory is typically an NFS-mounted location and must be accessible all specified installation systems.
|
-precheck
|
Performs a preinstallation check to determine if systems meet all installation requirements. Symantec recommends doing a precheck before installing a product.
|
-requiredpkgs
|
Displays all required product packages in correct installation order. Optional packages are not listed. Output can be used to create scripts for command line installs, or for installations over a network. See installpkgs option.
|
-responsefile response_file [-enckeyfile encryption_key_file]
|
Automates installation and configuration by using system and configuration information stored in a specified file instead of prompting for information. The response_file must be a full path name. If not specified, the response file is automatically generated as installerer number.response . number is random. You must edit the response file to use it for subsequent installations. Variable field definitions are defined within the file.
The -enckeyfile option and encryption_key_file name are required with the -responsefile option when the response file contains encrypted passwords.
|
-rootpath root_path
|
Specifies an alternative root directory on which to install packages.
On Solaris operating systems, -rootpath passes
-R path to pkgadd .
On HP-UX operating systems, -rootpath passes
-I path to swinstall .
The -rootpath option is not supported on AIX or Linux operating systems.
|
-rsh
|
Specify this option when you want to use RSH and RCP for communication between systems instead of the default SSH and SCP. The -rsh option requires that systems be preconfigured so that commands between systems execute without prompting for passwords or confirmations.
|
-tmppath tmp_path
|
Specifies a directory other than /var/tmp as the working directory for the installation scripts. This destination is where initial logging is performed and where packages are copied on remote systems before installation.
|