Commands Reference, Volume 3

ilverify Command

Syntax

ilverify [ -p SearchDirectory ] [ -e ExceptionFile ] [ -i Inslists ] [ -t TableName ] [ -d DbFileOut ] [ -n DbFileIn ]

The ilverify command validates inslist files. The ilverify command validates individual inslist files, or it searches a specified directory such as a build tree, a sandbox, or the current directory and validates all inslist (*.il) files found. Any errors detected are displayed to stderr.

The command searches for and uses prerequisite files (*.prereq.S) as part of the verification process. The information from multiple inslists is combined into an ordered list based on the prereq files before verification. The ilverify command then ensures that the following criteria holds across inslists:

The correct number of fields exist in each inslist entry.
The type field is valid in each inslist entry.
The UID and GID fields in the inslists entries are valid. (When this command is run with the -t flag, the UID and GID fields are checked using the specified table. The /etc/passwd and /etc/group files are used as default.)
A directory entry appears before any file or link entries for that directory.
All parent directories are specified in the inslists.
File paths that exist in one inslist entry do not exist in another inslist entry unless they are on the exception list. When this command is run with the -e flag, the exception list file specified is used. If the -e flag is not specified, the file indicated by the environment variable EXCEPTION_LIST is used if it exists.
Duplicate directory entries are identical; that is, they have identical attributes in all inslists if they exist.
Duplicate directory paths that are not identical do not exist unless they are on the exception list. When this command is run with the -e flag, the exception list file specified is used. If the -e flag is not specified, the file indicated by the environment variable EXCEPTION_LIST is used if it exists.
Hard links do not cross base file systems.

If neither the -i nor -p flags are specified, the inslists in the current directory are validated and a recursive directory search is not performed.

The ilverify command also generates a database file when invoked with the -d flag. The database file contains a composite list of the entries from all the inslists validated.

The output database file can be used as input with the -n flag to validate individual inslists against the database information. The database is assumed to be correct, so ilverify only runs its checks against the individual inslist files specified. If the -n flag is not specified, the file indicated by the environment variable DB_FILE_IN is used if it exists.

The -n and -d flags are mutually exclusive.

Note: Inslist verification against the input database file does not perform requisite directory checking. This is because ilverify does not have access to all of the necessary prereq.S files when an input database file is used.

Flags

Notes:

The inslists in the current directory are validated if the -p or -i flags are not specified. A recursive directory search for inslists is not performed.
A command line flag always overrides a prespecified environment variable.

-d DbFileOut	Specifies where to generate the composite database file of inslists.
-e ExceptionFile	Specifies the full path name of the exception file. This file contains the file path names that may exist in more than one inslist. The environment variable EXCEPTION_LIST can also be used to specify this file.
-i Inslists	Specifies individual inslists paths. Multiple entries are supported and must be separated by a colon (:).
-n DbFileIn	Specifies the name of an existing database file to be used when verifying the inslists. The environment variable DB_FILE_IN can also be used to specify this file.
-p SearchDirectory	Specifies the path to the build tree directory, the sandbox directory, or a search directory. A recursive directory search is performed for all inslists.
-t TableName	Specifies the name of a file that contains a table that is used to validate the UID and GID fields contained in the inslist entries. Any UIDs or GIDs that are not found in the table are verified against /etc/passwd and /etc/group on the running system.

Environment Variables

DB_FILE_IN	Specifies the full pathname of the existing database file.
EXCEPTION_LIST	Specifies the full pathname of the exception file.

Examples

Call ilverify to verify the inslists contained in the directory /project/aix4/build/latest/src/packages. The files and directory paths specified in /aix/4.1/sb/tmp/except.list may exist in more than one inslist, and a composite database file of all the inslist entries is generated into /aix/4.1/sb/tmp/db_file. Requisite directory checking is performed.
```
ilverify -p /project/aix4/build/latest/src/packages \ 
-e /aix/4.1/sb/tmp/except.list -d /aix/4.1/sb/tmp/db_file
```
Call ilverify to verify inslist1.il and inslist2.il. The table user.table is used to validate the UID and GID fields contained in these inslists. The composite database file /aix/4.1/sb/tmp/db_file is used to check for duplicate path definitions. Requisite directory checking is not performed.
```
ilverify -i /aix/4.1/sb/tmp/inslist1.il:/aix/4.1/sb/tmp/inslist2.il -t user.table \ 
-n /aix/4.1/sb/tmp/db_file
```

Input Files

*inslist(.il)**	This file contains the inslist entries for the objects related to each installable LPP. The format of this file is: type uid gid mode fileName Example: F 2 2 555 /usr/bin/grep The format of a symlink entry in the inslist is: type uid gid mode linkName targetFile Example: S 2 2 777 /usr/bin/fgrep /usr/bin/grep Hard link entries immediately follow the inslist entry of their target file. Hard links are considered attributes of the target file in the inventory database because they share the same inode as the target file. An example of an inslist entry with hard links is: F 2 2 555 /usr/bin/awk H 2 2 555 /usr/bin/nawk /usr/bin/awk
prereq file (option.prereq.S)	This file contains the prerequisite options for each installable product. These options must be installed prior to that product. The inslists being verified are ordered based on the required prerequisites. The format of this file is: # Prologue # prereq option* version.releasemodification level.fix level Example: *prereq bos.adt.cls 4.1.0.0
exception file	This file contains the file or directory path names that may exist in more than one inslist. The environment variable associated with this file is EXCEPTION_LIST. The format of this file is one path name per line.
uid/gid table	This file contains a table that can add to or supersede usr and group ID information for the system from /etc/passwd and /etc/group. ilverify validates UIDs/GIDs from the inslist first against this table (if specified) and then against /etc/passwd and /etc/group. The format of this file is: user name uid group name gid Example: dbadmuser 200 dbadmgroup 300

Output File

composite database

This file contains a composite list of all the inslists validated. This database file can be used on subsequent invocations of the command to validate individual inslists without having to perform a total verification of all inslists.