558 (3PROJECT)
559
560 These functions constitute the project database access library,
561 libproject. This library is implemented as a shared object,
562 libproject.so, but is not automatically linked by the C compilation
563 system. Specify -lproject on the cc command line to link with this
564 library. See libproject(3LIB).
565
566
567 (3RSM)
568
569 These functions constitute the remote shared memory library,
570 librsm. This library is implemented as a shared object, librsm.so,
571 but is not automatically linked by the C compilation system.
572 Specify -lrsm on the cc command line to link with this library. See
573 librsm(3LIB).
574
575
576 (3SCF)
577
578 These functions constitute the object-caching memory allocation
579 library, libscf. This library is implemented as a shared object,
580 libscf.so, but is not automatically linked by the C compilation
581 system. Specify -lscf on the cc command line to link with this
582 library. See libscf(3LIB).
583
584
585 (3SEC)
586
587 These functions constitute the file access control library, libsec.
588 This library is implemented as a shared object, libsec.so, but is
589 not automatically linked by the C compilation system. Specify -lsec
590 on the cc command line to link with this library. See libsec(3LIB).
591
592
593 (3SECDB)
594
595 These functions constitute the security attributes database
596 library, libsecdb. This library is implemented as a shared object,
597 libsecdb.so, but is not automatically linked by the C compilation
598 system. Specify -lsecdb on the cc command line to link with this
838 Many of these symbolic names describe boundary conditions and system
839 limits.
840
841
842 In this section, for readability, these implementation-specific values
843 are given symbolic names. These names always appear enclosed in curly
844 brackets to distinguish them from symbolic names of other
845 implementation-specific constants that are accessible to application
846 programs by headers. These names are not necessarily accessible to an
847 application program through a header, although they can be defined in
848 the documentation for a particular system.
849
850
851 In general, a portable application program should not refer to these
852 symbolic names in its code. For example, an application program would
853 not be expected to test the length of an argument list given to a
854 routine to determine if it was greater than {ARG_MAX}.
855
856
857
858 November 26, 2017 INTRO(3)
|
558 (3PROJECT)
559
560 These functions constitute the project database access library,
561 libproject. This library is implemented as a shared object,
562 libproject.so, but is not automatically linked by the C compilation
563 system. Specify -lproject on the cc command line to link with this
564 library. See libproject(3LIB).
565
566
567 (3RSM)
568
569 These functions constitute the remote shared memory library,
570 librsm. This library is implemented as a shared object, librsm.so,
571 but is not automatically linked by the C compilation system.
572 Specify -lrsm on the cc command line to link with this library. See
573 librsm(3LIB).
574
575
576 (3SCF)
577
578 These functions constitute the service configuration facility
579 library, libscf. This library is implemented as a shared object,
580 libscf.so, but is not automatically linked by the C compilation
581 system. Specify -lscf on the cc command line to link with this
582 library. See libscf(3LIB).
583
584
585 (3SEC)
586
587 These functions constitute the file access control library, libsec.
588 This library is implemented as a shared object, libsec.so, but is
589 not automatically linked by the C compilation system. Specify -lsec
590 on the cc command line to link with this library. See libsec(3LIB).
591
592
593 (3SECDB)
594
595 These functions constitute the security attributes database
596 library, libsecdb. This library is implemented as a shared object,
597 libsecdb.so, but is not automatically linked by the C compilation
598 system. Specify -lsecdb on the cc command line to link with this
838 Many of these symbolic names describe boundary conditions and system
839 limits.
840
841
842 In this section, for readability, these implementation-specific values
843 are given symbolic names. These names always appear enclosed in curly
844 brackets to distinguish them from symbolic names of other
845 implementation-specific constants that are accessible to application
846 programs by headers. These names are not necessarily accessible to an
847 application program through a header, although they can be defined in
848 the documentation for a particular system.
849
850
851 In general, a portable application program should not refer to these
852 symbolic names in its code. For example, an application program would
853 not be expected to test the length of an argument list given to a
854 routine to determine if it was greater than {ARG_MAX}.
855
856
857
858 August 19, 2019 INTRO(3)
|