HP-UX Reference (11i v2 07/12) - 1M System Administration Commands N-Z (vol 4)

s
swpackage(1M) swpackage(1M)
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.
Locking
SD commands use a common locking mechanism for reading and modifying both root directories and
software depots. This mechanism allows multiple readers but only one writer on a root or depot.
The SD commands which modify software in an (alternate) root directory are restricted from simultaneous
modification using fcntl() locking on the file
var/adm/sw/products/swlock
relative to the root directory (for example, /var/adm/sw/products/swlock
).
The SD commands which modify software in a depot are restricted from simultaneous modification using
fcntl() locking on the file
catalog/swlock
relative to the depot directory (for example, /var/spool/sw/catalog/swlock
).
All commands set
fcntl() read locks on roots and depots using the swlock file mentioned above.
When a read lock is set, it prevents other SD commands from performing modifications (that is, from set-
ting write locks).
PRODUCT SPECIFICATION FILE
This section summarizes the product_specification_file (PSF) which drives the
swpackage session. See
swpackage(4) for a detailed description of PSF syntax and semantics.
A PSF is structured as follows:
[depot specification]
[vendor specification]
[category specification]
[bundle specification]
[product specification]
[control script specification]
[subproduct specification]
[fileset specification]
[control script specification]
[file specification]
[fileset specification]
...
[product specification]
...
If errors encountered while parsing the PSF result in no valid product definitions,
swpackage ter-
minates. All errors are logged to both stderr and the logfile. In summary, the swpackage user can:
• Specify one or more products;
• For each product, specify one or more filesets.
• For each fileset, specify one or more files.
• (optional) Specify attributes for the target depot/tape;
• (optional) Specify one or more bundles, defining the bundle contents;
• (optional) Specify vendor information for products and bundles;
• (optional) Specify category information for products, bundles and patches.
• (optional) For each product, specify one or more subproducts, defining the subproduct contents;
• (optional) For each product or fileset, specify one or more control scripts.
RETURN VALUES
The swpackage command returns:
508 Hewlett-Packard Company − 9 − HP-UX 11i Version 2: December 2007 Update