swconfig(1M) swconfig(1M)
NAME [Toc] [Back]
swconfig - configure, unconfigure, or reconfigure installed software
SYNOPSIS [Toc] [Back]
swconfig [-p] [-u] [-v] [-c catalog] [-C session_file]
[-f software_file] [-J jobid] [-Q date] [-S session_file]
[-t target_file] [-x option=value] [-X option_file]
[software_selections] [@ target_selections]
Remarks [Toc] [Back]
+ This command supports operation on remote systems. See Remote
Operation below.
+ swconfig can perform limited interactive operations. See
Interactive Operation below.
+ For an overview of all SD commands, see the sd(5) man page by
typing man 5 sd on the command line.
DESCRIPTION [Toc] [Back]
The swconfig command configures, unconfigures, or reconfigures
installed software products for execution on the specified targets.
The swconfig command transitions software between INSTALLED and
CONFIGURED states. Although software is automatically configured as
part of the swinstall command and unconfigured as part of the swremove
command, swconfig lets you configure or unconfigure software
independently when the need arises.
Configuration primarily involves the execution of vendor-supplied
configure scripts. These scripts perform configuration tasks which
enable the use of the software on the target hosts. A vendor can also
supply unconfigure scripts to "undo" the configuration performed by
the configure script.
NOTES:
+ You should execute swconfig when an initial configuration by
swinstall failed, was deferred, or needs to be changed.
+ With swinstall, you can defer configuration by using the
defer_configure default option.
+ swinstall does not perform configuration on multiple versions
of software.
+ The swconfig command only operates on software installed to
the primary root file system.
+ swinstall and swremove do not run configure or unconfigure
scripts when you specify an alternate root directory with
those commands.
Hewlett-Packard Company - 1 - HP-UX 11i Version 2.0
swconfig(1M) swconfig(1M)
Other features of swconfig include:
+ By default, the swconfig command supports only configuration
of compatible software.
+ If a fileset specifies a prerequisite on other software, that
software must be in a "configured" state before the software
specifying the dependency will be configured.
+ The swconfig command configures multiple versions of a product
if you set allow_multiple_versions=true. The vendor must
therefore detect and prevent multiple configured versions in
their configure scripts, if that is necessary.
+ Configure scripts are useful for software updates and
reinstallation, as well as first-time installation.
Remote Operation [Toc] [Back]
You can enable Software Distributor (SD) to manage software on remote
systems. To let the root user from a central SD controller (also
called the central management server or 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 operations 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) Enable the GUI interfaces for remote operations by
creating the .sdkey file on the controller. Use this command:
touch /var/adm/sw/.sdkey
(This step is not required when you use SD from within the HP
ServiceControl Manager.)
Hewlett-Packard Company - 2 - HP-UX 11i Version 2.0
swconfig(1M) swconfig(1M)
NOTE: You can also set up remote access by using the swacl(1M) command
directly on the remote machines to grant root or non-root access to
users from the controller system.
Interactive Operation [Toc] [Back]
swconfig can perform limited interactive operations when the ask
option is set to true. This option executes an interactive request
script. Request scripts can also be executed by swinstall and swask.
See the ask=false default option for more information. See also
swinstall(1M) and swask(1M).
Options [Toc] [Back]
swconfig supports the following options:
-c catalog Specifies the pathname of an exported catalog
which stores copies of the response file or files
created by a request script (if -x ask=true or -x
ask=as_needed). Response files are also stored in
the Installed Products Database.
-C session_file
Save the current options and operands to
session_file. You can enter a relative or
absolute path with the file name. The default
directory for session files is
$HOME/.sw/sessions/. You can recall a session
file with the -S option.
-f software_file
Read the list of software_selections from
software_file instead of (or in addition to) the
command line.
-J jobid Executes the previously scheduled job. This is
the syntax used by the daemon to start the job.
-p Previews a configuration task by running the
session through the analysis phase only.
-Q date Schedules the job for this date. You can change
the date format by editing the
/var/adm/sw/getdate.templ file.
-S session_file
Execute swconfig based on the options and operands
saved from a previous session, as defined in
session_file. You can save session information to
a file with the -C option.
-t target_file Read the list of target_selections from
target_file instead of (or in addition to) the
Hewlett-Packard Company - 3 - HP-UX 11i Version 2.0
swconfig(1M) swconfig(1M)
command line.
-u Causes swconfig to unconfigure the software
instead of configuring it.
-v Turns on verbose output to stdout. (The swconfig
logfile is not affected by this option.) Verbose
output is enabled by default; see the verbose
option below.
-x option=value
Set the session option to value and override the
default value (or a value in an alternate
option_file specified with the -X option).
Multiple -x options can be specified.
-X option_file Read the session options and behaviors from
option_file.
Operands [Toc] [Back]
Most SD commands support two types of operands: software selections
followed by target selections. These operands are separated by the
"@" (at) character. This syntax implies that the command operates on
"software selections at targets".
Software Selections [Toc] [Back]
The swconfig command supports the following syntax for each
software_selection:
bundle[.product[.subproduct][.fileset]][,version]
product[.subproduct][.fileset][,version]
+ The = (equals) relational operator lets you specify
selections with the following shell wildcard and patternmatching
notations:
[ ], *, ?
+ Bundles and subproducts are recursive. Bundles can contain
other bundles and subproducts can contain other subproducts.
+ The \* software specification selects all products. Use this
specification with caution.
The version component has the form:
[,r <op> revision][,a <op> arch][,v <op> vendor]
[,c <op> category][,q=qualifier][,l=location]
[,fr <op> revision][,fa <op> arch]
Hewlett-Packard Company - 4 - HP-UX 11i Version 2.0
swconfig(1M) swconfig(1M)
+ location applies only to installed software and refers to
software installed to a location other than the default
product directory.
+ fr and fa apply only to filesets.
+ The <op> (relational operator) component can be of the form:
=, ==, >=, <=, <, >, or !=
which performs individual comparisons on dot-separated
fields.
For example, r>=B.10.00 chooses all revisions greater than
or equal to B.10.00. The system compares each dot-separated
field to find matches.
+ The = (equals) relational operator lets you specify
selections with the shell wildcard and pattern-matching
notations:
[ ], *, ?, !
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 (e.g. r>=A.12, r<A.20). If multiple
components are used, the selection must match all
components.
+ Fully qualified software specs include the r=, a=, and v=
version components even if they contain empty strings.
+ No space or tab characters are allowed in a software
selection.
+ The software instance_id can take the place of the version
component. It has the form:
[instance_id]
within the context of an exported catalog, where instance_id
is an integer that distinguishes versions of products and
bundles with the same tag.
The \* software specification selects all products. It is not allowed
when removing software from the root directory /.
Target Selections [Toc] [Back]
swconfig
Hewlett-Packard Company - 5 - HP-UX 11i Version 2.0
swconfig(1M) swconfig(1M)
supports this syntax for each target_selection.
[host][:][/directory]
The : (colon) is required if both a host and directory are specified.
EXTERNAL INFLUENCES [Toc] [Back]
Default Options
In addition to the standard options, several SD behaviors and policy
options can be changed by editing the default values found in:
/var/adm/sw/defaults the system-wide default values.
$HOME/.swdefaults the user-specific default values.
Values must be specified in the defaults file using this syntax:
[command_name.]option=value
The optional command_name prefix denotes one of the SD commands. Using
the prefix limits the change in the default value to that command. If
you leave the prefix off, the change applies to all commands.
You can also override default values from the command line with the -x
or -X options:
command -x option=value
command -X option_file
The following section lists all of the keywords supported by the
swlist commands. If a default value exists, it is listed after the
"=".
The policy options that apply to swconfig are:
admin_directory=/var/adm/sw (for normal mode)
admin_directory=/var/home/LOGNAME/sw (for nonprivileged mode)
The location for SD logfiles and the default parent
directory for the installed software catalog. The
default value is /var/adm/sw for normal SD operations.
When SD operates in nonprivileged mode (that is, when
the run_as_superuser default option is set to true):
+ The default value is forced to /var/home/LOGNAME/sw.
+ The path element LOGNAME is replaced with the name
of the invoking user, which SD reads from the system
password file.
Hewlett-Packard Company - 6 - HP-UX 11i Version 2.0
swconfig(1M) swconfig(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.
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.
See also the installed_software_catalog and
run_as_superuser options.
agent_auto_exit=true
Causes the target agent to automatically exit after
Execute phase, or after a failed Analysis phase. This
is forced to false when the controller is using an
interactive UI, or when -p (preview) is used. This
enhances network reliability and performance. The
default is true - the target agent will automatically
exit when appropriate. If set to false, the target
agent will not exit until the controller ends the
session.
agent_timeout_minutes=10000
Causes a target agent to exit if it has been inactive
for the specified time. This can be used to make
target agents more quickly detect lost network
connections since RPC can take as long as 130 minutes
to detect a lost connection. The recommended value is
the longest period of inactivity expected in your
environment. For command line invocation, a value
between 10 minutes and 60 minutes is suitable. A value
of 60 minutes or more is recommended when the GUI will
be used. The default of 10000 is slightly less than 7
days.
allow_incompatible=false
Requires that the software products which are being
configured be "compatible" with the target selections.
(All of the target selections must match the list of
Hewlett-Packard Company - 7 - HP-UX 11i Version 2.0
swconfig(1M) swconfig(1M)
supported systems defined for each selected product.)
If set to true, target compatibility is not enforced.
allow_multiple_versions=false
Prevents the configuration of another, independent
version of a product when a version already is
configured at the target.
If set to true, another version of an existing product
can be configured in its new location. Multiple
versions can only be installed if a product is
locatable. Multiple configured versions will not work
unless the product supports it.
ask=false When ask=true, executes a request script, which asks
for a user response. If ask=as_needed, the swask
command first determines if a response file already
exists in the control directory and executes the
request script only when a response file is absent.
If set to ask=true, or ask=as_needed, you can use the
-c catalog option to specify the pathname of an
exported catalog to store copies of the response file
or files created by the request script.
See swask(1M) for more information on request scripts.
autoremove_job=false
Controls automatic job removal of completed jobs. If
the job is automatically removed, job information (job
status or controller/agent logfiles) cannot be queried
with swjob.
autoselect_dependencies=true
Controls the automatic selection of prerequisite,
corequisite, and exrequisite software that is not
explicitly selected by the user. This option does not
apply to swconfig -u. The default is: true. The
requisite software will be automatically selected for
configuration. Specifying false causes requisite
software, which is not explicitly selected, to not be
automatically selected for configuration.
autoselect_dependents=false
Controls the automatic selection of dependent software
that is not explicitly selected by the user. A
dependent is the opposite of a requisite. A dependent
fileset has established either a prerequisite or a
corequisite on the selected fileset. Specifying true
causes dependent software to be automatically selected
for unconfiguration. The default, false causes
Hewlett-Packard Company - 8 - HP-UX 11i Version 2.0
swconfig(1M) swconfig(1M)
dependent software, which is not explicitly selected,
to not be automatically selected for unconfiguration.
compress_index=false
Determines whether SD commands create compressed INDEX
and INFO catalog files when writing to target depots or
roots. The default of false does not create compressed
files. When set to true, SD creates compressed and
uncompressed INDEX and INFO files. The compressed files
are named INDEX.gz and INFO.gz, and reside in the same
directories as the uncompressed files.
Compressed files can enhance performance on slower
networks, although they may increase disk space usage
due to a larger Installed Products Database and depot
catalog. SD controllers and target agents for HP-UX
11.01 and higher automatically load the compressed
INDEX and INFO files from the source agent when:
+ The source agent supports this feature.
+ INDEX.gz or INFO.gz exist on the source depot.
+ INDEX.gz or INFO.gz are not older than the
corresponding uncompressed INDEX or INFO files.
The uncompressed INDEX or INFO file is accessed by the
source agent if any problem occurs when accessing,
transferring, or uncompressing the INDEX.gz or INFO.gz
file.
controller_source
Location of a depot for the controller to access to
resolve selections. This has no effect on which sources
the target uses. Specify this as host, /path, or
host:/path. Useful for reducing network traffic between
controller and target.
enforce_dependencies=true
Requires that all dependencies specified by the
software_selections be resolved at the
target_selections.
The swconfig, command will not proceed unless the
dependencies have also been selected or already exist
at the target in the correct state (INSTALLED or
CONFIGURED). This prevents unusable software from
being configured on the system.
If set to false, dependencies will still be checked,
but not enforced. Corequisite dependencies, if not
Hewlett-Packard Company - 9 - HP-UX 11i Version 2.0
swconfig(1M) swconfig(1M)
enforced, may keep the selected software from working
properly. Prerequisite and exrequisite dependencies, if
not enforced, may cause the configuration to fail.
enforce_scripts=true
Controls the handling of errors generated by scripts.
If true, and the vendor-supplied script returns an
error, the configure or unconfigure operation stops. An
error message appears reporting that the execution
phase failed. If false, swconfig attempts to continue
operation. A warning message appears reporting that the
execution succeeded.
installed_software_catalog=products
Defines the directory path where the Installed Products
Database (IPD) is stored. This information describes
installed software. When set to an absolute path, this
option defines the location of the IPD. When this
option contains a relative path, the SD controller
appends the value to the value specified by the
admin_directory option to determine the path to the
IPD. For alternate roots, this path is resolved
relative to the location of the alternate root. This
option does not affect where software is installed,
only the IPD location.
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. (This
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.)
job_title=
This is an ASCII string giving a title to a job. It is
displayed along with the job ID to provide additional
identifying information about a job when swjob is
invoked.
Hewlett-Packard Company - 10 - HP-UX 11i Version 2.0
swconfig(1M) swconfig(1M)
log_msgid=0
Adds numeric identification numbers at the beginning of
SD logfile messages:
0 (default) No identifiers are attached to messages.
1 Adds identifiers to ERROR messages only.
2 Adds identifiers to ERROR and WARNING messages.
3 Adds identifiers to ERROR, WARNING, and NOTE
messages.
4 Adds identifiers to ERROR, WARNING, NOTE, and
certain other informational messages.
logdetail=false
Controls the amount of detail written to the logfile.
When set to true, this option adds detailed task
information (such as options specified, progress
statements, and additional summary information) to the
logfile. This information is in addition to log
information controlled by the loglevel option.
See loglevel below and the sd(5) manual page, by typing
man5sd, for more information.
logfile=/var/adm/sw/swconfig.log
This is the default command log file for the swconfig
command.
loglevel=1
Controls the log level for the events logged to the
command logfile, the target agent logfile, and the
source agent logfile. This information is in addition
to the detail controlled by the logdetail option. (See
logdetail above and the sd(5) manual page, by typing
man 5 sd , for more information.) A value of
0 provides no information to the logfile.
1 enables verbose logging to the logfiles.
2 enables very verbose logging to the logfiles.
mount_all_filesystems=true
By default, the swconfig command attempts to
automatically mount all filesystems in the /etc/fstab
file at the beginning of the analysis phase, to ensure
that all listed filesystems are mounted before
proceeding. This policy helps to ensure that files are
not loaded into a directory that may be below a future
mount point.
If set to false, the mount operation is not attempted,
and no check of the current mounts is performed.
Hewlett-Packard Company - 11 - HP-UX 11i Version 2.0
swconfig(1M) swconfig(1M)
reconfigure=false
Prevents software which is already in the CONFIGURED
state from being reconfigured. If set to true,
CONFIGURED software can be reconfigured.
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 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.
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 the
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.
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.)
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
file system permissions.
+ SD ACLs are ignored.
+ Files created by SD have the uid and gid of the
invoking user, and the mode of created files 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
Hewlett-Packard Company - 12 - HP-UX 11i Version 2.0
swconfig(1M) swconfig(1M)
nonprivileged SD, see the Software Distributor
Administration Guide, available at the
http://docs.hp.com web site.
See also the admin_directory and
installed_software_catalog options.
select_local=true
If no target_selections are specified, select the local
host as the target of the command.
software= Defines the default software_selections. There is no
supplied default. If there is more than one software
selection, they must be separated by spaces.
targets= Defines the default target_selections. There is no
supplied default (see select_local above). If there is
more than one target selection, they must be separated
by spaces.
verbose=1 Controls the verbosity of the output (stdout). A value
of
0 disables output to stdout. (Error and warning
messages are always written to stderr).
1 enables verbose messaging to stdout.
write_remote_files=false
Prevents the configuring of files on a target which
exists on a remote (NFS) filesystem. All files on a
remote filesystem will be skipped.
If set to true and if the superuser has write
permission on the remote filesystem, the remote files
will not be skipped, but will be configured.
Session File [Toc] [Back]
Each invocation of the swconfig command defines a configuration
session. The invocation options, source information, software
selections, and target hosts are saved before the installation or copy
task actually commences. This lets you re-execute the command even if
the session ends before proper completion.
Each session is automatically saved to the file
$HOME/.sw/sessions/swremove.last. This file is overwritten by each
invocation of swconfig.
You can also save session information to a specific file by executing
swconfig with the -C session__file option.
A session file uses the same syntax as the defaults files. If you do
not specify a specific path for the session file, the default location
Hewlett-Packard Company - 13 - HP-UX 11i Version 2.0
swconfig(1M) swconfig(1M)
is $HOME/.sw/sessions/.
To re-execute a session file, specify the session file as the argument
for the -S session__file option of swconfig.
Note that when you re-execute a session file, the values in the
session file take precedence over values in the system defaults file.
Likewise, any command line options or parameters that you specify when
you invoke swconfig take precedence over the values in the session
file.
Environment Variables [Toc] [Back]
The environment variable that affects the swconfig command is:
LANG Determines the language in which messages are
displayed. If LANG is not specified or is set to the
empty string, a default value of C is used. See
lang(5) for more information.
NOTE: The language in which the SD agent and daemon log
messages are displayed is set by the system
configuration variable script, /etc/rc.config.d/LANG.
For example, /etc/rc.config.d/LANG, must be set to
LANG=ja_JP.SJIS or LANG=ja_JP.eucJP to make the agent
and daemon log messages display in Japanese.
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 (e.g., single-versus multibyte
characters in values for vendor-defined attributes).
LC_MESSAGES [Toc] [Back]
Determines the language in which messages should be
written.
LC_TIME Determines the format of dates (create_date and
mod_date) when displayed by swlist. Used by all
utilities when displaying dates and times in stdout,
stderr, and logging.
TZ Determines the time zone for use when displaying dates
and times.
Environment variables that affect scripts are:
SW_CATALOG [Toc] [Back]
Holds the path to the Installed Products Database
(IPD), relative to the path in the SW_ROOT_DIRECTORY
Hewlett-Packard Company - 14 - HP-UX 11i Version 2.0
swconfig(1M) swconfig(1M)
environment variable. Note that you can specify a path
for the IPD using the installed_software_catalog
default option.
SW_CONTROL_DIRECTORY [Toc] [Back]
Defines the current directory of the script being
executed, either a temporary catalog directory, or a
directory within in the Installed Products Database
(IPD). This variable tells scripts where other control
scripts for the software are located (e.g. subscripts).
SW_CONTROL_TAG [Toc] [Back]
Holds the tag name of the control_file being executed.
When packaging software, you can define a physical name
and path for a control file in a depot. This lets you
define the control_file with a name other than its tag
and lets you use multiple control file definitions to
point to the same file. A control_file can query the
SW_CONTROL_TAG variable to determine which tag is being
executed.
SW_LOCATION [Toc] [Back]
Defines the location of the product, which may have
been changed from the default product directory. When
combined with the SW_ROOT_DIRECTORY, this variable
tells scripts where the product files are located.
SW_PATH A PATH variable which defines a minimum set of commands
available for use in a control script (e.g.
/sbin:/usr/bin).
SW_ROOT_DIRECTORY [Toc] [Back]
Defines the root directory in which the session is
operating, either "/" or an alternate root directory.
This variable tells control scripts the root directory
in which the products are installed. A script must use
this directory as a prefix to SW_LOCATION to locate the
product's installed files. The configure script is
only run when SW_ROOT_DIRECTORYis /.
SW_SESSION_OPTIONS [Toc] [Back]
Contains the pathname of a file containing the value of
every option for a particular command, including
software and target selections. This lets scripts
retrieve any command options and values other than the
ones provided explicitly by other environment
variables. For example, when the file pointed to by
SW_SESSIONS_OPTIONS is made available to a request
script, the targets option contains a list of
software_collection_specs for all targets specified for
the command. When the file pointed to by
Hewlett-Packard Company - 15 - HP-UX 11i Version 2.0
swconfig(1M) swconfig(1M)
SW_SESSIONS_OPTIONS is made available to other scripts,
the targets option contains the single
software_collection_spec for the targets on which the
script is being executed.
SW_SOFTWARE_SPEC [Toc] [Back]
This variable contains the fully qualified software
specification of the current product or fileset. The
software specification allows the product or fileset to
be uniquely identified.
Signals [Toc] [Back]
The swconfig command catches the signals SIGQUIT and SIGINT, and
SIGUSR1. If these signals are received, swconfig prints a message,
sends a Remote Procedure Call (RPC) to the agents to wrap up, and then
exits.
The agent ignores SIGHUP, SIGINT, and SIGQUIT. It immediately exits
gracefully after receiving SIGTERM, SIGUSR1, or SIGUSR2. Killing the
agent may leave corrupt software on the system, and thus should only
be done if absolutely necessary. Note that when an SD command is
killed, the agent does not terminate until completing the task in
progress.
The daemon ignores SIGHUP, SIGINT and SIGQUIT. It immediately exits
gracefully after receiving SIGTERM and SIGUSR2. After receiving
SIGUSR1, it waits for completion of a copy or remove from a depot
session before exiting, so that it can register or unregister depots
if necessary. Requests to start new sessions are refused during this
wait.
Each agent will complete the configuration task (if the execution
phase has already started) before it wraps up. This avoids leaving
software in a corrupt state.
RETURN VALUES [Toc] [Back]
The swconfig command returns:
0 The software_selections were successfully configured.
1 The configure operation failed on all target_selections.
2 The configure operation failed on some target_selections.
DIAGNOSTICS [Toc] [Back]
The swconfig command writes to stdout, stderr, and to specific
logfiles.
Standard Output [Toc] [Back]
The swconfig command writes messages for significant events. These
include:
Hewlett-Packard Company - 16 - HP-UX 11i Version 2.0
swconfig(1M) swconfig(1M)
+ a begin and end session message,
+ selection, analysis, and execution task messages for each
target_selection.
Standard Error [Toc] [Back]
The swconfig command also writes messages for all WARNING and ERROR
conditions to stderr.
Logging [Toc] [Back]
The swconfig command logs summary events at the host where the command
was invoked. It logs detailed events to the swagent logfile
associated with each target_selection.
Command Log
The swconfig command logs all stdout and stderr messages to the
the logfile /var/adm/sw/swconfig.log. (The user can specify a
different logfile by modifying the logfile option.)
Target Log
A swagent process performs the actual configure operation at each
target_selection. The swagent logs events to the file
/var/adm/sw/swagent.log. You can view the command and target log
files with the swjoborsd command.
EXAMPLES [Toc] [Back]
Configure the C and Pascal products on the local host:
swconfig cc pascal
Configure Product1, use any associated response files generated by a
request script, and save response files under /tmp/resp1:
swconfig -x ask=true -c /tmp/resp1 Product1
Reconfigure the HP Omniback product:
swconfig -x reconfigure=true Omniback
Configure the version of HP Omniback that was installed at
/opt/Omniback_v2.0:
swconfig Omniback,l=/opt/Omniback_v2.0
Unconfigure the software_selections listed in the file
/tmp/install.products on the hosts listed in the file
/tmp/install.hosts:
swconfig -u -f /tmp/install.products -t /tmp/install.hosts
Configure the C and Pascal products on remote hosts:
Hewlett-Packard Company - 17 - HP-UX 11i Version 2.0
swconfig(1M) swconfig(1M)
swconfig cc pascal @ hostA hostB hostC
LIMITATIONS [Toc] [Back]
The SD-UX version of swconfig does not support the configuration,
unconfiguration, or reconfiguration of installed software on remote
targets.
FILES [Toc] [Back]
$HOME/.swdefaults
Contains the user-specific default values for some or all SD
software management command options.
$HOME/.sw/sessions/
Contains session files automatically saved by the SD software
management commands, or explicitly saved by the user.
/usr/lib/sw/sys.defaults
Contains the master list of current SD options with their
default values.
/var/adm/sw/
The directory which contains all configurable and nonconfigurable
data for SD software management commands. This
directory is also the default location of logfiles.
/var/adm/sw/defaults
Contains the active system-wide default values for some or all
SD software management command options.
/var/adm/sw/getdate.templ
Contains the set of date/time templates used when scheduling
jobs.
/var/adm/sw/products/
The Installed Products Database (IPD), a catalog of all
products installed on a system.
AUTHOR [Toc] [Back]
swconfig was developed by the Hewlett-Packard Company.
SEE ALSO [Toc] [Back]
swpackage(4), swacl(1M), swagentd(1M), swask(1M), swcopy(1M),
swinstall(1M), swjob(1M), swlist(1M), swmodify(1M), swpackage(1M),
swreg(1M), swremove(1M), swverify(1M) install-sd(1M), sd(4), sd(5).
Software Distributor Administration Guide, available at
http://docs.hp.com.
SD customer web site at http://software.hp.com/SD_AT_HP/.
Hewlett-Packard Company - 18 - HP-UX 11i Version 2.0
swconfig(1M) swconfig(1M)
Hewlett-Packard Company - 19 - HP-UX 11i Version 2.0 [ Back ] |
