HP-UX Reference (11i v1 05/09) - 1M System Administration Commands N-Z (vol 4)

ManualsBrandsHP ManualsSoftwareHP-UX Reference Manuals

411

412

413

414

415

416

417

418

419

420

swinstall(1M) swinstall(1M)

(HP-UX Software Distributor)

The reinstall_files

option should also be set to false to avoid installing ﬁles within

the ﬁleset 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

speciﬁed 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.

retry_rpc_interval={0}

Speciﬁes 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 speciﬁed in

retry_rpc. If the number of

values in

retry_rpc_interval

is less than the value in

retry_rpc, SD repeats the

ﬁnal interval value until the number of retries matches

retry_rpc.

For example, if a 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 ﬁrst 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 ﬁle 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 ﬁve times over a 30-minute period.

rpc_binding_info=ncacn_ip_tcp:[2121] ncadg_ip_udp:[2121]

Deﬁnes the protocol sequence(s) and endpoint(s) on which the daemon listens and the other

commands 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. See the sd(5) man page by typing

man 5 sd for

more information.

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 give faster recognition on attempts to con-

tact hosts that are not up or 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 when using the

ncacn_ip_tcp protocol sequence.

run_as_superuser=true

This option controls SD’s nonprivileged mode. This option is ignored (treated as true) when

the invoking user is super-user.

When set to the default value of true, SD operations are performed normally, with permis-

sions for operations either granted to a local super-user or set by SD ACLs. (See swacl(1M)

for details on ACLs.)

When set to false and the invoking user is local and is not super-user, nonprivileged mode

is invoked:

• Permissions for operations are based on the user’s ﬁle system permissions.

• SD ACLs are ignored.

• Files created by SD have the uid and gid of the invoking user, and the mode of created

ﬁles is set according to the invoking user’s umask.

SD’s nonprivileged mode is intended only for managing applications that are specially

designed and packaged. This mode cannot be used to manage the HP-UX operating system

or patches to it. For a full explanation of nonprivileged SD, see the Software Distributor

Administration Guide, available at the

http://docs.hp.com

web site.