HP-UX Reference (11i v1 05/09) - 5 Miscellaneous Topics (vol 9)

s
sd(5) sd(5)
(HP-UX Software Distributor)
the source causes the task to abort. If set from 1 to 9, then the install of each fileset will be
attempted that number of times. (You can use the
retry_rpc_interval
option to
specify the length of the interval between each retry attempt.)
The
reinstall_files
option should also be set to false to avoid installing files within
the fileset that were successfully installed.
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_interval
option 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 tries reestablishing 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 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 SD 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, 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
retry_rpc was set to 5 and retry_rpc_interval
was set to {1 2 4 8 15}, the con-
troller would try to contact the target five times over a 30-minute period.
Applies to
swcopy and swinstall.
rpc_binding_info=ncacn_ip_tcp:[2121] ncadg_ip_udp:[2121]
Defines the protocol sequence(s) and endpoint(s) on which the daemon listens and on which
the other commands use to contact the daemon. If the connection fails for one protocol
sequence, the next is attempted. SD supports both the tcp
(ncacn_ip_tcp:[2121])
and udp (ncadg_ip_udp:[2121]) protocol
sequence on most platforms.
The value (or values for
swagentd) can have following form:
• A DCE string binding containing a protocol sequence and an endpoint. The syntax is:
protocol_sequence:[endpoint]
.
• The name of a DCE protocol sequence with no endpoint specified. The syntax is:
protocol_sequence
, for example ncadg_ip_udp or ncacn_ip_tcp .(A
trailing
: can be attached to the protocol sequence, it has no effect.) Since no end-
point is specified, the DCE endpoint mapper rpcd must be running and will be used to
find the endpoint registered by the swagentd.
• The literal string all. This entry means to use (try) all protocol sequences supported
by the DCE RPC. It should be the only entry in the list. The DCE endpoint mapper
rpcd also must be running in order to use this option.
Applies to all commands except swask, swpackage, and swmodify.
rpc_binding_info_alt_source=ncadg_ip_udp:[2121]
Defines the protocol sequence(s) and endpoint(s) used when the agent attempts to contact
an alternate source depot specified by the alternate_source option. SD supports
both the udp(ncadg_ip_udp:[2121]) and tcp(ncacn_ip_tcp:[2121]
) protocol
sequence/endpoint.
Applies to
swagent.
rpc_timeout=5
Relative length of the communications timeout. This is a value in the range from 0 to 9 and
is interpreted by the DCE RPC. Higher values mean longer times; you may need a higher
value for a slow or busy network. Lower values will give faster recognition on attempts to
contact hosts that are not up, or are not running swagentd. Each value is approximately
Section 5−−328 Hewlett-Packard Company − 23 − HP-UX 11i Version 1: September 2005