Print this page
11582 3SCF isn't the object-caching memory allocation library

Split Close
Expand all
Collapse all
          --- old/usr/src/man/man3/Intro.3.man.txt
          +++ new/usr/src/man/man3/Intro.3.man.txt
↓ open down ↓ 567 lines elided ↑ open up ↑
 568  568  
 569  569             These functions constitute the remote shared memory library,
 570  570             librsm. This library is implemented as a shared object, librsm.so,
 571  571             but is not automatically linked by the C compilation system.
 572  572             Specify -lrsm on the cc command line to link with this library. See
 573  573             librsm(3LIB).
 574  574  
 575  575  
 576  576         (3SCF)
 577  577  
 578      -           These functions constitute the object-caching memory allocation
      578 +           These functions constitute the service configuration facility
 579  579             library, libscf. This library is implemented as a shared object,
 580  580             libscf.so, but is not automatically linked by the C compilation
 581  581             system. Specify -lscf on the cc command line to link with this
 582  582             library. See libscf(3LIB).
 583  583  
 584  584  
 585  585         (3SEC)
 586  586  
 587  587             These functions constitute the file access control library, libsec.
 588  588             This library is implemented as a shared object, libsec.so, but is
↓ open down ↓ 259 lines elided ↑ open up ↑
 848  848         the documentation for a particular system.
 849  849  
 850  850  
 851  851         In general, a portable application program should not refer to these
 852  852         symbolic names in its code. For example, an application program would
 853  853         not be expected to test the length of an argument list given to a
 854  854         routine to determine if it was greater than {ARG_MAX}.
 855  855  
 856  856  
 857  857  
 858      -                               November 26, 2017                      INTRO(3)
      858 +                                August 19, 2019                       INTRO(3)
    
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX