swask.1m (2012 03)

ManualsBrandsHP ManualsSoftwareHP-UX Manpages

swask(1M) swask(1M)

NAME

swask - ask for user response

SYNOPSIS

swask [-v][-c catalog ][

-C session_ﬁle ][-f software_ﬁle ][-J jobid ][

-Q date ]

[

-s source ][-S session_ﬁle ][

-t target_ﬁle ][-x option=value ][-X options_ﬁle ]

[ software_selections ][

@ target_selections]

Remarks

• This command supports operation on remote systems. See Remote Operation below.

• For an overview of all SD commands, see the sd(5) man page by typing

man5sdon the com-

mand line.

DESCRIPTION

The

swask command runs interactive software request scripts for the software objects selected to one or

more targets speciﬁed by target_selections. These scripts store the responses in a response ﬁle (named

response) for later use by the swinstall

and swconfig commands. The swinstall and swcon-

fig commands can also run the interactive request scripts directly, using the

ask option.

When

HP-UX Containers (SRP) is installed and enabled, the

swask command behavior is changed

to support software management for system containers. (For more information on HP-UX Containers,

refer to the srp (1M) and container_system(5) manpages.)

If the

-s option is speciﬁed, software is selected from the distribution source. If the

-s option is not

speciﬁed, software installed on the target systems is selected. For each selected software that has a

request script, executing that script generates a response ﬁle. By specifying the

-c catalog option,

swask stores a copy of the response ﬁle to that catalog for later use by swinstall

or swconfig.

Remote Operation

You can enable SD to manage software on remote systems. To let the root user from a central SD con-

troller (also called the central management server or IR "manager node" ) perform operations on a remote

target (also called the host or agent ):

1) Set up the root, host, and template Access Control Lists (ACLs) on the remote machines to permit

root access from the controller system. To do this, run the following command on each remote sys-

tem:

/usr/lib/sw/mx/setaccess

controller

NOTES:

• controller is the name of the central management server.

• If remote system is 11.00, make sure SD patch PHCO_22526 or a superseding patch is installed

on remote system before running

setaccess.

• If remote system is older than 11.00 or for some other reason does not have

setaccess in place,

copy setaccess script from an 11.11 or higher system to the remote system.

swinstall, swcopy, and swremove have enhanced GUI interfaces for remote operations. Enable

the enhanced GUIs by creating the .sdkey ﬁle on the controller. Use this command:

touch /var/adm/sw/.sdkey

See sd(5), swinstall (1M), swcopy(1M), swjob(1M), swlist (1M), or swremove (1M) for more information

on interactive operations.

NOTE: You can also set up remote access by using

swacl directly on the remote machines to grant root

or non-root access to users from the controller system.

Options

The

swask command supports the following options:

-v Turns on verbose output to stdout.

-c catalog Speciﬁes the pathname of an exported catalog which stores the response ﬁles

created by the request script. swask creates the catalog if it does not already exist.

If the -c catalog option is omitted and the source is local,

swask copies the response

ﬁles into the source depot, <distribution.path>/catalog .

HP-UX 11i Version 3: March 2012 − 1 − Hewlett-Packard Company 1

Summary of content (10 pages)

PAGE 1
swask(1M) swask(1M) NAME swask - ask for user response SYNOPSIS swask [-v] [-c catalog ] [-C session_file ] [-f software_file ] [-J jobid ] [-Q date ] [-s source ] [-S session_file ] [-t target_file ] [-x option=value ] [-X options_file ] [ software_selections ] [@ target_selections] Remarks • This command supports operation on remote systems. See Remote Operation below. • For an overview of all SD commands, see the sd(5) man page by typing man 5 sd on the command line.
PAGE 2
swask(1M) swask(1M) -C session_file Saves the current options and operands only to the session_file . You can enter a relative or absolute path with the file name. The default directory for session files is $HOME/.sw/sessions/. Without this option, by default, the session file is saved only in the default directory $HOME/.sw/sessions/. You can recall a session file with the -S option.
PAGE 3
swask(1M) swask(1M) [ ], *, ?, ! For example, the expression r=1[01].* returns any revision in version 10 or version 11. • All version components are repeatable within a single specification (for example, r>=AA.12, r
PAGE 4
swask(1M) swask(1M) • If you set the value of this option to HOME/path , SD replaces HOME with the invoking user’s home directory (from the system password file) and resolves path relative to that directory. For example, HOME/my_admin resolves to the my_admin directory in your home directory. • If you set the value of the installed_software_catalog default option to a relative path, that path is resolved relative to the value of this option.
PAGE 5
swask(1M) swask(1M) This option permits the simultaneous installation and removal of multiple software applications by multiple users or multiple processes, with each application or group of applications using a different IPD. Caution: use a specific installed_software_catalog to manage a specific application. SD does not support multiple descriptions of the same application in multiple IPDs. See also the admin_directory and run_as_superuser options, which control SD’s nonprivileged mode.
PAGE 6
swask(1M) swask(1M) 0 If there were no warnings and no errors. 1 If there were errors. 2 If there were warnings but no errors. 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 permissions for operations either granted to a local super-user or set by SD ACLs. (See swacl (1M) for details on ACLs.
PAGE 7
swask(1M) swask(1M) LC_ALL Determines the locale to be used to override any values for locale categories specified by the settings of LANG or any environment variables beginning with LC_. LC_CTYPE Determines the interpretation of sequences of bytes of text data as characters (for example, single versus multibyte characters in values for vendor-defined attributes). LC_MESSAGES Determines the language in which messages should be written.
PAGE 8
swask(1M) 2 swask(1M) Command failed on some targets DIAGNOSTICS The swask command writes to stdout, stderr, and to the swask logfile. Standard Output An interactive swask session does not write to stdout. A non-interactive swask session writes messages for significant events. These include: • • a begin and end session message, selection, analysis, and execution task messages for each target_selection. Standard Error An interactive swask session does not write to stderr.
PAGE 9
swask(1M) swask(1M) /var/adm/sw/products/ The Installed Products Database (IPD), a catalog of all products installed on a system. /var/adm/sw/swask.log Contains all stdout and stderr messages generated by swask. AUTHOR swask was developed by the Hewlett-Packard Company. SEE ALSO swconfig(1M), swinstall(1M), sd(5). Software Distributor Administration Guide , available at http://docs.hp.com. SD customer web site at http://docs.hp.com/en/SD/.
PAGE 10
(Notes) A (Notes) sA 10 Hewlett-Packard Company −1− HP-UX 11i Version 3: March 2012