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:
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).
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.
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.
Do not check for run level.
Abort installation if run level is not met.
Do not check for conflict; files in conflict will be overwritten.
Abort installation if conflict is detected.
Override installation of conflicting files; they will not be installed.
Do not check for setuid executables.
Abort installation if setuid processes are detected.
Override installation of setuid processes; processes will be installed without setuid bits enabled.
Ignore security impact of action scripts.
Abort installation if action scripts may have a negative security impact.
Do not check for a partially installed package.
Abort installation if a partially installed package exists.
Exit without installing if an instance of the package already exists (does not overwrite existing packages).
Overwrite an existing package if only one instance exists. If there is more than one instance, but only one has the same architecture, it overwrites that instance. Otherwise, the installer is prompted with existing instances and asked which to overwrite.
Do not overwrite an existing instance of a package. Instead, a new instance of the package is created. The new instance will be assigned the next available instance identifier.
Do not check package dependencies.
Abort installation if package dependencies are not met.
Do not check package dependencies.
Abort removal if package dependencies are not met.
Do not check space requirements (installation fails if it runs out of space).
Abort installation if space requirements are not met.
Below is a sample admin file.
basedir=default runlevel=quit conflict=quit setuid=quit action=quit partial=quit instance=unique idepend=quit rdepend=quit space=quit
The value ask should not be defined in an admin file that will be used for non-interactive installation (since by definition, there is no installer interaction). Doing so causes installation to fail when input is needed.