admin – installation defaults file
admin is a generic name for an ASCII file that defines default installation actions by
assigning values to installation parameters. For example, it allows administrators to
define how to proceed when the package being installed already exists on the system.
/var/sadm/install/admin/default is the default admin file delivered with this
release. The default file is not writable, so to assign values different from this file,
create a new admin file. There are no naming restrictions for admin files. Name the
file when installing a package with the -a option of pkgadd(1M). If the -a option is
not used, the default admin file is used.
Each entry in the admin file is a line that establishes the value of a parameter in the
following form:
param=value
Eleven parameters can be defined in an admin file, but it is not required to assign
values to all eleven parameters. If a value is not assigned, pkgadd(1M) asks the
installer how to proceed.
The eleven parameters and their possible values are shown below except as noted.
They may be specified in any order. Any of these parameters (except the mail
parameter) can be assigned the value ask, which means that if the situation occurs the
installer is notified and asked to supply instructions at that time (see NOTES).
basedir Indicates the base directory where relocatable packages are to be
installed. If there is no basedir entry in the file, the installer will
be prompted for a path name, as if the file contained the entry
basedir=ask. This parameter can also be set to default (entry
is basedir=default). In this instance, the package is installed
into the base directory specified by the BASEDIR parameter in the
pkginfo(4) file.
mail Defines a list of users to whom mail should be sent following
installation of a package. If the list is empty, no mail is sent. If the
parameter is not present in the admin file, the default value of
root is used. The ask value cannot be used with this parameter.
runlevel Indicates resolution if the run level is not correct for the
installation or removal of a package. Options are:
nocheck Do not check for run level.
quit Abort installation if run level is not met.
conflict Specifies what to do if an installation expects to overwrite a
previously installed file, thus creating a conflict between packages.
Options are:
admin(4)
NAME
DESCRIPTION
18 man pages section 4: File Formats • Last Revised 7 Feb 1997
