sd.5 (2011 03)

s
sd(5) sd(5)
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 the
setaccess script from an 11.11 or higher system to the remote system.
2) swinstall
, swcopy, and swremove have enhanced GUI interfaces for remote operations.
Enable the enhanced GUIs by creating the
.sdkey
file on the controller. Use this command:
touch /var/adm/sw/.sdkey
NOTE: You can also set up remote access by using the
swacl command directly on the remote machines
to grant root or non-root access to users from the controller system.
Interactive Operation
By default, all SD commands except
sd and
swask operate in a non-interactive mode. The
swcopy,
swinstall, swlist, and swremove commands also support a graphical user interface (GUI). (If your
terminal or display cannot support the GUI, these commands also provide a terminal user interface, in
which screen navigation is done with the keyboard and no mouse.)
To invoke the GUI, enter the command without any command-line options or add the
-i option with
other command-line options when you invoke the command. You must specify the
-i option to invoke
the swlist GUI.
The
swconfig and the command-line version of swinstall work interactively when the
ask option
is set to
true. This option executes an interactive request script .
The
sd command is an interactive interface for monitoring and scheduling software jobs. It provides the
same functionality as the
swjob command. You can also use sd to invoke the swinstall, copy, and
swremove GUIs.
If you have enabled SD’s remote operations features,
swinstall, swcopy, and
swremove provide
enhanced GUIs to support operations on remote targets. See
Remote Operation above for details
about enabling remote operations and the enhanced GUIs.
Distributed Operation
All SD commands except
swask, swpackage, and swmodify use a distributed model of operation.
The commands act as the controller for distributed operations, managing the specific software manage-
ment tasks. For each target_selection, an SD agent process performs the task:
•
swagent - perform software management tasks as the agent of an SD command.
Communication between the command and each agent, plus other target host activities are facilitated by
an SD daemon process:
•
swagentd - serve local or remote software management tasks.
Software Job Management
The
swinstall, copy, and remove commands create job information that records the job definition
(in a session file), status, and log information for the job. You can execute jobs immediately, or schedule
them for later execution. You can browse the scheduled, active, and completed jobs using either the
swjob command or the sd interactive interface.
Secure Operation
SD uses Access Control Lists (ACLs) to authorize users attempting to create, modify, or read software
products in a depot or installed to a root file system. The superuser can grant specific local and remote
users specific access permissions to a target host, a target depot, and/or a target root file system. (Note
that SD does not use ACLs for tasks invoked by a local root user.)
Because files are loaded and scripts are run as superuser, granting write permission (to install software)
on a root file system or insert permission (to create a new root) on a host, effectively gives the user
superuser privileges.
SD uses a method based on credentials and passwords to authenticate the user and the SD command per-
forming a given operation.
2 Hewlett-Packard Company − 2 − HP-UX 11i Version 3: March 2011