Open System Services Management and Operations Guide (G06.25+, H06.03+)

Managing OSS Files
Open System Services Management and Operations Guide527191-002
6-9
Removing Obsolete OSS Files and Directories
and should be ignored. Using PINSTALL on such files would overwrite current files
with obsolete ones.
PINSTALL is installed as a part of the basic OSS product set and is available even
if the subvolume containing COPYOSS has been deleted from your system.
Under rare conditions, the PINSTALL command can return an error message that
indicates a disk file could not be found; this message can be ignored when the
named file is an empty directory in the corresponding pax archive file. You can use
the -cvf flags of the PINSTALL command to display the table of contents for the
pax archive to determine if the named file is actually an empty directory.
Files installed by PINSTALL are not always secured in conformance with the best
practices at your site. You should always resecure files installed by PINSTALL. For
example, after installing SQL/MX files, you might enter commands such as the
following to secure the installed software and the directories it uses:
find / -WNOE -WNOG \( -type d -o -type f \) -perm -o+w |
xargs chmod o-w
chmod a=rwxt /tmp /usr/tmp /var/tmp /var/preserve
/usr/tandem/sqlmx/USERMODULES
Beginning with SPR T8626AAY and the G06.08 RVU, the PINSTALL utility should
not be used to install individual pax archives for these products:
°
T8626
°
T8627
°
T8628
Use the COPYOSS utility instead. COPYOSS performs special processing for
those products.
When circumstances force the use of PINSTALL instead of COPYOSS for these
products, the operator must manually run the utility /bin/replace immediately
after installing the T8626 pax archive RELUTILS, then remove the
/bin/replace utility from the OSS file system.
This consideration was removed beginning with SPR T8626ABH and the G06.15
RVU.
Removing Obsolete OSS Files and Directories
When you update OSS products, you might need to remove files from previous RVUs.
The installation process places files containing lists of obsolete files in the directory
/etc/install_obsolete. If:
DSM/SCM installed and maintains the OSS product files in your OSS file system,
you should do nothing with these files. Attempting to use the files for maintenance
will invalidate DSM/SCM database information about OSS product files on your
system.