solaris crle命令和信任机制

在原有信任基础上追加：
solaris9:

# crle

Default configuration file (/var/ld/ld.config) not found
  Default Library Path (ELF):   /usr/lib  (system default)
  Trusted Directories (ELF):    /usr/lib/secure  (system default)

# crle -s /lib -u

# crle

Configuration file [version 4]: /var/ld/ld.config 
  Default Library Path (ELF):   /usr/lib  (system default)
  Trusted Directories (ELF):    /usr/lib/secure:/lib

Command line:
  crle -c /var/ld/ld.config -s /usr/lib/secure:/lib

追加信任库后,找不到libgcc_s.so.1,将/usr/lib下的libgcc_s.so.1 拷贝到/lib下.

SunOS 5.9           Last change: 10 Oct 2001                    5

User Commands                                             crle(1)

           this option are permitted,  the  directory  dir  being
           used   to   locate   alternatives  for  any  following
           command-line options. Alternative objects are not per-
           mitted to override their associated originals.

     -s dir
           This option specifies a new trusted directory dir  for
           secure ELF or AOUT objects. See SECURITY in ld.so.1(1)
           for a definition of secure objects.

           Multiple occurrences of this option are permitted. The
           type  of  object applicable to the search is specified
           by the preceding -t option, or defaults to ELF.

           The system default trusted directory  for  secure  ELF
           objects  is  /usr/lib/secure  for  32-bit  objects and
           /usr/lib/secure/64  for  64-bit  objects.  The  system
           default  trusted  directories  for secure AOUT objects
           are    /usr/4lib,    /usr/lib,    /usr/ucblib,     and
           /usr/local/lib.

           Use of this option replaces the system default trusted
           directories,  and  thus it is normally required that a
           -s option be  used  to  specify  the  original  system
           default  in  relation  to  any  new  directories being
           applied. However, if the -u option is in effect, and a
           configuration file does not exist, the system defaults
           are added to the new configuration file before the new
           directories specified with the -s option.

     -u    This option requests  that  a  configuration  file  be
           updated,  possibly  with  the addition of new informa-
           tion. Without other options any existing configuration
           file  is  inspected and its contents recomputed. Addi-
           tional arguments allow information to be  appended  to
           the recomputed contents. See NOTES.

           If a configuration file does  not  exist  it  will  be
           created  as  directed  by  the other arguments. In the
           case of the -l and -s options any system defaults will
           first  be applied to the configuration file before the
           directories specified with these options.