sd.5 (2011 03)

s
sd(5) sd(5)
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 reestablish-
ing 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
controller 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 pro-
tocol 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 trail-
ing
: can be attached to the protocol sequence, it has no effect.) Since no endpoint 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_binding_info_source=
Defines the protocol sequence(s) and endpoint(s) used to contact the daemon for source
access. If set to no value (default) the value of rpc_binding_info is used.
Applies to
swinstall and swcopy.
rpc_binding_info_target=
Defines the protocol sequence(s) and endpoint(s) used to contact the daemon for target
access. If set to no value (default) the value of rpc_binding_info is used.
Applies to
swinstall and swcopy.
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 twice as long as the preceding value. A value of 5 is about 30 seconds for
the ncadg_ip_udp protocol sequence. This option may not have any noticeable impact
HP-UX 11i Version 3: March 2011 − 23 − Hewlett-Packard Company 23