stl_sts man page on DigitalUNIX

Man page or keyword search:  
man Server   12896 pages
apropos Keyword Search (all sections)
Output format
DigitalUNIX logo
[printable version]

stl_sts(4)							    stl_sts(4)

NAME
       stl_sts - setld subset status file

DESCRIPTION
       The  setld  utility  generates a subset status file, subset.sts, before
       installing each subset.	This  file  describes  the  software  subset's
       installation  status,  reflecting  the  success	or failure of specific
       setld utility processing phases. The setld utility removes  the	subset
       status file after the software subset is deleted.

       The  /usr/.smdb./subset.sts  file  is a symbolic link to the /usr/clus‐
       ter/members/{memb}/.smdb./subset.sts file.

       The following list describes possible values in	subset	status	files:
       The  software is not on the system. Either the subset was not installed
       or it was deleted successfully.	The setld utility is in the process of
       deleting the software. The setld -d process has not completed or failed
       to delete the subset.  The setld utility failed	in  the	 PRE_L	phase.
       Although the software did not load onto the system, some system changes
       may have been made.  The setld utility finished the PRE_L phase and the
       software is ready to load onto the system.  The software is loaded onto
       the system, but one or  more  of	 the  files  failed  the  verification
       process and the software is not installed and cannot be used. The veri‐
       fication process compares the size and checksum of the file on the sys‐
       tem  against  the inventory record. If either value does not match, the
       file fails verification.	 The software is loaded onto the  system;  all
       of  the subset files are present and verified.  The software is not yet
       installed on the system, as the POST_L and C INSTALL  phases  must  run
       and  protected  system files must be moved into place.  The software is
       loaded onto the system but the  setld  utility  failed  in  the	POST_L
       phase.  The subset files are present but the software is not installed.
       The software is loaded onto the system and the setld utility  completed
       the  POST_L  phase.  The	 subset	 files are present and the software is
       ready to be configured in the C INSTALL	phase.	 This  status  applies
       only  to	 clusters.  The software is loaded onto the cluster, the setld
       utility completed the POST_L phase, but failed to finish	 copying  mem‐
       ber-specific  information  to  the  current cluster member. The current
       cluster member has all of the shared files but not all of  the  member-
       specific	 files.	 This status applies only to clusters. The software is
       loaded onto the cluster, the setld utility completed the POST_L	phase,
       and  all	 member-specific files were copied to the current cluster mem‐
       ber. The software is ready to be configured in the C INSTALL  phase  on
       the current cluster member.  The software is loaded onto the system but
       the setld utility failed in the C INSTALL phase. The subset  files  are
       present	but  the  software  is not configured or installed.  The setld
       utility completed the C INSTALL phase and the software is installed  on
       the system. There are no other installation steps required by the setld
       utility, although the software may require additional setup before use.
       The subset status file is corrupted and an unsupported string cannot be
       mapped to a valid state. This is a serious condition  and  may  require
       that you remove and reinstall the software.

       For  information	 about	failure	 recovery  when you install and delete
       software subsets, refer to the Installation Guide.

RESTRICTIONS
       The values in the subset status file are text strings  that  correspond
       to  an  internal	 code  state. These values are not identical to either
       this internal code state or to the subset status displayed in the  out‐
       put of the setld -i command.

       Do not use the contents of the subset status file as input to a program
       such as a subset control program (SCP) that needs to  determine	subset
       status.	 The values in the subset status file reflect an internal code
       state and can change to reflect updated requirements, while the	inter‐
       nal  code  states  are constant. For additional information about using
       internal code states to determine subset status, refer to the Guide  to
       Preparing Product Kits.

FILES
       Symbolic	 link  to  member-specific  subset status file Member-specific
       subset status file for subset subset

SEE ALSO
       Commands: setld(8)

       Files: stl_scp(4)

       Guide to Preparing Product Kits

       Installation Guide

       TruCluster Server Cluster Installation

								    stl_sts(4)
[top]

List of man pages available for DigitalUNIX

Copyright (c) for man pages and the logo by the respective OS vendor.

For those who want to learn more, the polarhome community provides shell access and support.

[legal] [privacy] [GNU] [policy] [cookies] [netiquette] [sponsors] [FAQ]
Tweet
Polarhome, production since 1999.
Member of Polarhome portal.
Based on Fawad Halim's script.
....................................................................
Vote for polarhome
Free Shell Accounts :: the biggest list on the net