HP-UX Reference (11i v1 00/12) - 1M System Administration Commands N-Z (vol 4)
__________________________________________________________________________________________________________________________________________________________________________________________________
__________________________________________________________________________________________________________________________________________________________________________________________________
STANDARD Printed by: Nora Chuang [nchuang] STANDARD
/build/1111/BRICK/man1m/naaagt.1m
________________________________________________________________
___ ___
s
swask(1M) swask(1M)
(Hewlett-Packard Company)
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 com-
mand line.
DESCRIPTION
The swask command runs interactive software request scripts for the software objects selected to one or
more targets specified by target_selections. These scripts store the responses in a response file (named
response) for later use by the swinstall and swconfig commands. The swinstall and
swconfig commands can also run the interactive request scripts directly, using the
ask option.
If the
-s option is specified, software is selected from the distribution source. If the
-s option is not
specified, software installed on the target systems is selected. For each selected software that has a request
script, executing that script generates a response file. By specifying the
-c catalog option, swask stores a
copy of the response file 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) Install a special HP ServiceControl Manager fileset on the remote systems. This enables remote opera-
tions by automatically setting up the root, host, and template Access Control Lists (ACLs) on the
remote machines and permitting root access from the controller system. To install the fileset, run the
following command on each remote system:
swinstall -s controller:/var/opt/mx/depot11 AgentConfig.SD-CONFIG
NOTES:
• controller is the name of the central management server.
• If the target is running HP-UX 10.20, use the same command but substitute depot10 for
depot11.
• Targets previously set up by SD/OV to be managed by this controller do not need this step.
• SD does not require any other ServiceControl Manager filesets.
2) (Optional) swinstall, swcopy, and swremove have enhanced GUI interfaces for remote opera-
tions. Enable the enhanced GUIs by creating the .sdkey file on the controller. Use this command:
touch /var/adm/sw/.sdkey
NOTES:
• This step is not required when you use SD from within the HP ServiceControl Manager.
• 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 Specifies the pathname of an exported catalog which stores the response files created
by the request script. swask creates the catalog if it does not already exist.
Section 1M−−848 − 1 − HP-UX Release 11i: December 2000
___
___