genufi(8) [osf1 man page]

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

NAME

       genufi - Generates a User File Inventory (UFI) file

SYNOPSIS

       /usr/bin/genufi

DESCRIPTION

       The genufi utility creates a User File Inventory (UFI) file that contains the names of user files created or copied to your system after an
       installation.  Some of these files reside on file systems that are overwritten during a new installation of the operating system. You  must
       have superuser privileges to run the genufi utility, and you must invoke the genufi utility from the /usr/.smdb.  directory.

       To  create the UFI file, the genufi utility checks the Master Synchronization Inventory (MSI) file created by the invsync utility to deter-
       mine which file systems will be overwritten by a complete installation.	The genufi utility searches those file systems for user files  and
       writes these entries to the UFI file.  File systems that remain intact during a new installation of the operating system are not searched.

       The  genufi utility also filters out certain files and directories that would not commonly be considered for backup.  For example, some log
       files, installation files, and temporary directories do not need to be restored after a complete installation and are not  written  to  the
       UFI file.

       The following directories are not included:

       /tmp /tmp /usr/.smdb.  /usr/sys/HOST /var/adm/smlogs /var/adm/syslog.dated /var/rwho /var/tmp

       In the previous list, HOST represents the hostname of the system (such as /usr/sys/BLUTO) on the system named bluto.

       The following files are not included:

       */core */*.dummy */.new..  /osf_boot */.profile */.proto..  /var/adm/binary.errlog /var/adm/xdm/xdm-pid */vmcore /*vmunix

       Edit  the  UFI  file  to remove the entries for files and directories that you do not want to back up. The UFI file is written in the setld
       inventory file format.  Refer to the stl_inv(4) reference page for more information.

RESTRICTIONS

       You must have superuser privileges to run the genufi utility.

       You must invoke the genufi utility from the /usr/.smdb.	directory.

FILES

       Master Synchronization Inventory file User File Inventory file

SEE ALSO

       ils(8), invsync(8), udelta(8), udetect(8), updmv(8), usync stl_inv(4)

																	 genufi(8)

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

NAME

       cdslinvchk - Checks the CDSL inventory of the base operating system and layered applications.

SYNOPSIS

       /usr/sbin/cdslinvchk [log_file_path]

OPTIONS

       The path name to a location for the log file.  By default this will be /var/adm/cdsl_check_list.

DESCRIPTION

       Use  the cdslinvchk script to verify the current inventory of Context Dependent Symbolic Links (CDSLs) on a running system.  CDSLs are spe-
       cial symbolic links that enable a system to work in a cluster.  If CDSLs are accidentally removed, your system will not function  correctly
       in  a cluster.  While this is not a problem for stand-alone systems, you may not be able to add the system as a member of a working cluster
       at some future time.  You can run this script at any time or configure it to run at system start-up, or as a cron task.

       When you invoke the script, it checks the CDSLs on the running system against CDSLs of the installed inventory in /usr/.smdb and the  addi-
       tional  entries	in  /var/adm/cdsl_admin.inv, and ensures that each target file exists on the system as a properly-constituted CDSL. If the
       check is successful, the following message is displayed and the script terminates: Successful CDSL inventory check

       If the script finds inconsistencies in the inventory, warning messages are displayed on your terminal and logged to the default log file at
       /var/adm/cdsl_check_list.   You	can specify an alternate location for the log fill if required.  The script locates any modified, missing,
       or replaced CDSLs.  Note that the previous copy of the log file is renamed and retained for reference and is renamed by	appending  to  the
       filename.

       Refer  to  the  System Administration guide for information on recreating any missing or broken CDSLs.  Refer to the hier(5) reference page
       for an inventory of CDSLs.

   MESSAGES
       One or more of the following messages may be displayed and logged to the log file: Unable to create <pathname> report file  --  the  script
       was  not able to create a log file.  Check the target directory and security.  Expected CDSL: <cdsl_pathname> -> <pathname> CDSL Target has
       been modified to: <pathname> CDSL has been replaced with <pathname> CDSL is missing Failed CDSL inventory check. See details in <log file>

FILES

       Additional inventory file entries.  This file will not exist on all systems.  The current and previous log files for inventory  errors  and
       messages

SEE ALSO

       Commands: cron(8)

       Others: hier(5)

       See also the System Administration guide for details of CDSLs

																     cdslinvchk(8)