Software Distributor Administration Guide HP-UX 11i v1, 11i v2, and 11i v3 (5900-2561, March 2013)

through 9. A 0 value means no retry is attempted; if the connection is lost, the command will fail.
The default value is 1. For less stable networks, a value of 5 is recommended.
NOTE: When setting retry_rpc to a value greater than 0, the reinstall_files option
should also be set to false (the default value), so the same files are not recopied when a fileset
is retried.
The maximum possible amount of time spent waiting for the timeout is affected by a combination
of rpc_timeout, retry_rpc, and retry_rpc_interval.
For troubleshooting information on Timeout options, refer to “Connection Timeouts and Other WAN
Problems ” (page 266).
8.5 Retry RPC and Retry Interval
During a swinstall or swcopy operation, retry_rpc_interval controls the interval schedule
for repeated attempts to make a connection to a target or the source agent after an initial failure.
This option works in conjunction with retry_rpc, which controls the number of times the target
or source is re-contacted.
The default value for retry_rpc is 1 and retry_rpc_interval is {0}.
The recommended values for the retry_rpc_interval algorithm are {1 2 4 8 15} with
retry_rpc set at 5. If the agent session fails to start for any reason, the controller and/or target
will attempt to re-connect in the following way (i.e., both options set as above):
• after 1 minute for the first try
• then 2 minutes for the second try
• then 4 minutes
• then 8 minutes
• finally 15 minutes for the last try
If the number of values for retry_rpc_intervalis less than retry_rpc, the last value given
is repeated until the number of actual retries is equal to retry_rpc.
NOTE: If retry_rpc has a value of zero, no retry is attempted. An initial value of 5 is
recommended for WAN environments.
8.6 Retry Command
SD-UX supports options that facilitate retrying operations that have failed. These can be used in
conjunction with the checkpointing features or can start the task from the beginning.
Each execution of a command records all of the target, software, and option selections automatically
in a session file, command.last. You can also save the session information to a different file using
the GUI. The session files are stored in the directory $HOME/.sw/sessions. The entire command
can be retried by recalling the session in the GUI or by re-executing the task:
command -S command.last
When a task is retried, any fileset that is up to date (has the same product and filesets revisions
as available or installed and is not in the transient or corrupt state) will not attempt to be reinstalled
(the default behavior), and all other filesets will be retried. This behavior can be overridden, forcing
the retry to start at the beginning of all files, by setting reinstall=true from either your option
setting or the CLI.
If the reinstall_files option is set to true, all files in that fileset are retransferred. However,
although preinstall and postinstall scripts for filesets that are being installed are executed normally,
the file transfer for up to date files can be avoided by leaving the reinstall_files option
equal to false (the default).
8.5 Retry RPC and Retry Interval 139