Login or Register to Ask a Question and Join Our Community

Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

fitset(8) [ultrix man page]

fitset(8)						      System Manager's Manual							 fitset(8)

Name
       fitset - determine if subset fits on a system

Syntax
       fitset [ -d ] [ root-path ]

Description
       The utility is used to determine if the files in a software subset will fit on a system.

       Subset inventory records are read from the standard input. For each record, the space required to install the file described in that record
       is deducted from the available free space on the file system to which it would be installed.  Only currently mounted UFS file  systems  are
       used  in  the computations. Space requirements for files already on the disk will be modified to account for the size of the resident copy.
       After all records have been read, the free space computed for all file systems is checked. If the space required to install the files would
       cause any file system to be more than 90% full, returns an exit status of -1.

       The  utility  uses  to size all 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.

Options
       -d     Enable debugging. This will make 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 been deducted.

Restrictions
       NFS mounts are ignored. If software would be installed to an NFS mounted directory, it is sized against the file system containing the  NFS
       mount point.

       The  program  does  not	detect the use of symbolic links in paths to root-path or any of the mount points. This can cause to size a subset
       incorrectly if root-path is a symbolic link or a symbolic link exists in the path of any of the pathnames used with the	command  to  mount
       local file systems.

Examples
       To determine if a particular subset will fit on the system, redirect the contents of the subset inventory file into For example:
	   fitset < /usr/etc/subsets/ULTUUCP400.inv

       To determine if the same subset will fit in a hierarchy rooted at the command would be:
	   fitset /var/tmp/root < /usr/etc/subsets/ULTUUCP400.inv

Diagnostics
       fitset: root path must be absolute
       A relative pathname was specified for root-path.  This path must be absolute.

       fitset: cannot stat root-path (error message)
       The root-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.

Files
       Subset inventory files

See Also
       stl_inv(5), setld(8)
       Guide to Preparing Software for Distribution on ULTRIX Systems

																	 fitset(8)

Check Out this Related Man Page

invcutter(1)						      General Commands Manual						      invcutter(1)

Name
       invcutter - generate subset inventory files

Syntax
       /usr/sys/dist/invcutter [ -d ] [ -f root-path ] [ -f version-code ]

Description
       The  command  reads master inventory records from standard input.  A subset inventory record is written to standard output for every record
       read from the input. The information contained in the output record is derived from the input record and the file attribute information	in
       the file hierarchy rooted in the current directory.

Options
       -d		   Enable debugging. No useful diagnostics are printed.

       -f root-path	   Specify an alternate root path for finding file attribute information.

       -v version-code	   Specify a 3-digit version code for use in the version field of the output records. The default version code is 010.

Restrictions
       All input records must be sorted in ascending order on the pathname field.

       Files described in an input record which exist as sockets in the file hierarchy are not processable.

       If a file is described in an input record has a link count greater than 1, all other links to the file must be represented in the input.

Examples
       The following command will generate inventory records for the master inventory entries in PDS020.mi containing version fields set to 020:
	   invcutter -v 020 < PDS020.mi

Return Values
       An exit status of 0 is returned if all goes well. An exit status of 1 is returned if an error occurs. See Diagnostics.

Diagnostics
       "cannot chdir to pathname (error-message)"
       The  program  cannot  change  directories to the pathname directory specified with the -f option. The error-message will provide additional
       information.

       "sort error, record #n"
       The nth input record is not in the correct sort order. All input records must be in ascending  ASCII  colating  sequence  on  the  pathname
       field.

       "cannot stat filename (error-message)"
       An error has occurred attempting to read the attributes of filename.  The error-message explains exactly what happened.

       "pathname: illegal file type code 0140000"
       The file pathname is a socket. Sockets are not supported as valid file types for distribution.

       "unresolved nlink n: pathname"
       This indicates that file pathname in the master inventory is linked to n files which do not appear in the master inventory. Check inventory
       for validity with the program.

       "n unresolved hard links"
       This is an informational message stating how many files were detected in the input inventory which had unresolved links.

See Also
       newinv(1), stl_inv(5), stl_mi(5)
       Guide to Preparing Software for Distribution on ULTRIX Systems

																      invcutter(1)
Man Page