Software Distributor (SD-UX) Administration Guide HP-UX 11i v1, 11i v2, and 11i v3 (762797-001, March 2014)

The depot's swagent.log file and directory structure are not removed by default. If the
swagent.log file and directory should be removed, the remove_empty_depot_directory
option must also be set to “true”.
If set to false, the depot is not removed when the last product (or bundle) in it is removed. This
preserves that depot’s ACL.
Applies only to swremove.
• remove_empty_depot_directory=false
If false (default), the depot's swagent.log file and directory are not removed when the last
product (or bundle) in the depot is removed.
If the remove_empty_depot_directory and the remove_empty_depot options are set to true,
and the last product (or bundle) in a depot is removed, the depot's swagent.log file and
directory are also removed.
Applies to swremove.
• remove_obsolete_filesets=false
This command controls whether swcopy and swpackage automatically remove obsolete
filesets from target products in the target depot.
If set to true, swcopy and swpackage remove obsolete filesets from the target products that
were written during the copy or package process. Removal occurs after the copy or package
is complete. Filesets are defined as obsolete if they were not part of the most recent packaging
of the product residing on the source depot or during the current packaging of the product
defined in the source PSF.
Applies to swcopy and swpackage.
• remove_setup_cmd=/usr/lbin/sw/remove_setup
Defines the script called by the agent to perform release-specific removal preparation. For an
OS update, this script invokes the tlink command when a fileset is removed.
Applies only to swagentd.
• retry_rpc=1
This command defines the number of times a lost source connection is retried during file
transfers. If set from 1 to 9, the install of each fileset is attempted that number of times. The
reinstall_files option should also be set to false to avoid installing files that were
successfully installed within the fileset.
This option also applies to the controller contacting the agent. If the agent session fails to start
for any reason, the controller tries to recontact that agent for the number of times specified in
retry_rpc, using the values from the retry_rpc_intervaloption to determine how long
to wait between each attempt to recontact the agent.
Applies to swcopy and swinstall.
• retry_rpc_interval={0}
Specifies in minutes the length of the interval for repeated attempts to make a connection to
a target after an initial failure. Used in conjunction with the retry_rpc option.
If the number of values in this option equals the value of retry_rpc, SD-UX tries to reestablish
a source connection for the number of times specified in retry_rpc. If the number of values
in retry_rpc_interval is less than the value in retry_rpc, SD-UX repeats the final
interval value until the number of retries matches retry_rpc.
For example, if an agent session failed to start and retry_rpc was set to 9 and
retry_rpc_interval was set to {1 2 4 8 15} to allow long waits to handle transient
network failures, the controller would attempt to recontact the agent after 1 minute for the first
retry, then 2 minutes for the second retry, 4 for the third retry, then 8, then 15 for all additional
retries until nine retries were attempted. With these values, a file load failure could cause the
operation to pause for 90 minutes (1+2+4+8+15+15+15+15+15). If both options were set
to 5, the controller would try to contact the target five times over a 30-minute period.
246 Command Options