fitset - determines if a software subset fits on a system
/usr/lbin/fitset [-c] [-d] [root-path]
This switch allows a file containing inventory records to
be passed in as an argument in addition to the standard
input. When this option is specified, fitset takes the
inventory records in the file and reclaims the file system
space and inodes they take up. Enables debugging. This
option makes fitset print voluminous status information on
standard output. This information is the initial file
system statistics, the file system location of the file
from each input record, and the statistics for the file
system after the space required to install the file has
The fitset utility is used to determine if the files in a
software subset will fit on a system.
The fitset utility reads software subset inventory records
from the standard input and calculates the number of
inodes and the amount of disk space the software subset
requires. For each record, fitset deducts one inode from
the number available in the target file system. For the
space calculation, fitset deducts the file size specified
by each record. Only currently mounted file systems are
included in the computations.
Space requirements for files already on the disk are
adjusted by using the difference between the specified
size and the size of the file that is already present.
A given software subset can include files that are to be
installed in several file systems. The fitset utility
tracks inodes and file space for all file systems affected
and returns nonzero status if the remaining number of
inodes or amount of free space for any of these file systems
is overflowed. If there is no overflow, fitset
returns a status of zero.
The setld utility uses fitset to size all software subsets
before attempting to install them. The root-path argument
is the pathname of the top directory for the hierarchy
into which the files are going to be installed. If no
root-path is specified, the directory '/' is assumed.
fitset: root-path must be absolute
A relative pathname was specified for root-path.
The path must be absolute. fitset: cannot access
The path cannot be accessed. The error message
provides more information. fitset: root-path is
not a directory.
Either root-path is not a directory or it is a symbolic
link to something which is not a directory.
fitset: <warning> path is a symbolic link to itself
The path is a symbolic link that involves cyclic
linking. fitset: file system path needs nnn Kbytes
more to install the software specified. fitset:
file system path needs nnn more inodes to install
the software specified.
The file system path is out of space. The message
that is displayed indicates whether the error is
insufficient space or a lack of available inodes.
fitset: file system path is not writable.
The mode of the file system named by path does not
permit writing into the file system.
To determine if a particular software subset will fit on
the system, redirect the contents of the software subset
inventory file into fitset. For example: fitset <
/usr/.smdb./OSFEMACS350.inv To determine if the same software
subset will fit in a hierarchy rooted at
/var/tmp/root, the command would be: fitset /var/tmp/root
< /usr/.smdb./OSFMANOP350.inv To determine if a particular
software subset will fit on the system after the removal
of another software subset, the command would be: fitset
-c /usr/.smdb./OSFMANOS350.inv < /usr/.smdb./OSFMANOP350.inv
Subset inventory files Log file
Guide to Preparing Product Kits
[ Back ]