Software Distributor Administration Guide (March 2009)

Table Of Contents
12.1.3 Limitations
Remote targets are not allowed with SD-UX remote operations, except for swlist
access to remote systems and commands that can normally access remote depots.
Access to such remote systems is determined by the SD ACLs on the remote system.
Nonprivileged mode cannot be used to manage HP-UX operating system software
or patches to it.
A swinstall or swcopy in nonprivileged mode cannot read a source depot on
a local writable file system that was created with super-user privileges (that is,
created by a super-user, or created by a non super-user when the
run_as_superuser option is set to true and using ACL permissions). This
limitation does not apply to tape or CD-ROM source depots.
swinstall and swcopy in nonprivileged mode can read any remote source depot
as allowed by ACLs, can read local source depots created by the invoking user in
nonprivileged mode, and (depending on the umask of other users) can read local
source depots created by other users in nonprivileged mode.
12.2 Setting Up Nonprivileged Mode
Nonprivileged SD is controlled by two options:
admin_directory
run_as_superuser
The run_as_superuser option turns nonprivileged mode on or off and is all that is
necessary to run the default configuration. (See “Turning On Nonprivileged Mode”
(page 297) and “Default Configuration” (page 297).)
The admin_directory option lets you set up an alternative configuration. (See
Alternative Configuration” (page 298).)
12.2.1 Packaging Software for Use in Nonprivileged Mode
In addition to these options, software applications to be used under nonprivileged
mode have special packaging requirements.
For nonprivileged mode to function:
You must package applications and install them so that the files are installed in
locations writable by the user who will install the applications. This can be done
by:
Using the directory keyword in the PSF during packaging
By appending a location to the software specifications when you invoke a
command from the command line. (See “Software Selections” (page 47).)
Scripts packaged into the application must be designed not to require super-user
privilege.
296 Nonprivileged SD